Description
Please select the type of request
Bug
Tell us more
Splunk Operator Version: 2.1.1
** Splunk Version: 9.0.2**
Describe the request
I have appframework referencing addon .tgz packages with their suffixed _$version. This of course becomes problematic when trying to upgrade the addon. I made a mistake of using the file names with the new _$version suffixed. I would like to have the operator reference a new file addon .tgz package without the suffxed _$version . I have tried everything:
- Deleted old suffixed files in s3
- Deleted artifact files on the operator that still referenced the suffxed files
- I killed the operator pod
- I killed the standalone, I even deleted its Standalone CR in UAT
- These suffixed files are also referenced by other Splunk components like SH's and indexers, kicking these in Prod would be problematic for me
What are the non-invasive steps to have the operator use the new file package without suffixed versions, so that it checks against the new file rather than trying to check against old artifact files? This way I can go back to each addon having the same file name and I can then easily upgrade the addons. Otherwise addons cannot be upgraded as the operator I believe doesn't recognize them as upgradable.
Expected behavior
The operator refrences new non suffixed file name and is able to upgrade the existing addon deployed on various splunk components.
Splunk setup on K8S
Splunk is set up on-prem k8's cluster
Reproduction/Testing steps
Install addon through appframework with version suffixed. Install the same addon with a newer version suffixed. Point appfrmework to a newer version. The addon will not upgrade!
Now try to fix this by removing suffixed version and simply use non suffix version in hopes of fixing the problem for future upgrades when the same name should be used instead of suffixed name. It doesn't work!