Question: Best practice for upgrading Trivy Operator with Helm #2767
Replies: 2 comments
-
|
Good day! No opinion or answer on this? |
Beta Was this translation helpful? Give feedback.
0 replies
-
Yes it is. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Good day,
I have been using the Trivy Operator for the past six months across several Kubernetes clusters. It has been a great experience and a very powerful tool for identifying vulnerabilities, helping us update much faster where necessary.
There is one area I’m unsure about, and I’d like to clarify:
I install the Trivy Operator using Helm and update it about once a month. I’ve been following the documentation here:
Upgrade guide
The docs state:
“However, at this stage we do not provide automated upgrades. Therefore, uninstall the previous version of the operator before you install the latest release.”
So my current process is:
Uninstall Trivy Operator.
Manually remove all CRDs as described here: Uninstall guide
Reinstall the new version with my values.yaml.
My question is: Is this still the recommended approach, or is there now a way to safely use
helm upgrade --installinstead of fully uninstalling and reinstalling?Thanks in advance for clarifying!
Beta Was this translation helpful? Give feedback.
All reactions