Upgrade policy for prometheus operator #3953
Replies: 3 comments 4 replies
-
There are plenty of upgrade scenarios tested in CI, so if that's your worry waiting is unlikely to increase upgrade confidence. Of course, new features may have an impact, but typically new features tend to be new fields, so one could say it's feature gates almost. We at Polar Signals just upgrade to whatever latest version is available in kube-prometheus, and that hasn't caused any issues. |
Beta Was this translation helpful? Give feedback.
-
Not seeing an answer. |
Beta Was this translation helpful? Give feedback.
-
Is there documentation on the best way to update? I installed with Helm and I'm not comfortable with just updating everything all at once. If there's an error how do I revert back? and other concerns. It'd be nice if there was a clear guide. 1) Update crds first? Then roles? |
Beta Was this translation helpful? Give feedback.
-
Hi Team,
We are using prometheus operator in our production clusters. We can see that there are frequent releases for prometheus operator. Wanted to understand what is the best approach of upgrading it. Should we update it to version n(latest) or n-1 or n-2 whenever we plan our next upgrade.
Appreciate your response.
Beta Was this translation helpful? Give feedback.
All reactions