New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Generated grafana deployment cannot be upgraded without downtime #381
Comments
This should be relabeled as a bug. strategy:
rollingUpdate:
maxSurge: 25%
maxUnavailable: 25%
type: RollingUpdate the operator generates it instead like this, which translates to 25 replicas updating at once, so it's not possible to have no downtime if running grafana with less than 26 replicas strategy:
rollingUpdate:
maxSurge: 25
maxUnavailable: 25
type: RollingUpdate Extract from k8s documentation, the value can be either absolute or percentace (int or string):
|
Hi @mariusstaicu , Thanks for bringing this up, I've done a bit of testing locally and it seems like switching
to use |
Is your feature request related to a problem? Please describe.
Whenever I change something to the grafana.yml spec file and redeploy, the operator upgrades all the replicas at once, hence there's no deployment update possible without downtime.
I suspect this is because the deployment is generated with RollingUpdate strategy with max surge / max unavailable 25. This causes all the replicas to be updated at once, which defeats the purpose of having multiple replicas.
(If applicable)If your feature request solves a bug please provide a link to the community issue
didn't find any issue reported on this matter before
Describe the solution you'd like
Leave the update strategy default - type RollingUpdate with maxSurge 25% and maxUnavailable 25% or implement an update strategy that doesn't cause all pods to be updated at once.
Describe alternatives you've considered
n/a
Additional context
Add any other context or screenshots about the feature request here.
Existing solutions
If applicable please provide a link to an existing solution from a different project
The text was updated successfully, but these errors were encountered: