-
Notifications
You must be signed in to change notification settings - Fork 704
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
Dangerous upgrade from 1.6.0 to 1.7.0 if the procedure is not followed #4734
Comments
How exactly did you do the upgrade? If I simply run
Which should prompt users to investigate further and hopefully discover our upgrade instructions. (I tried this on OCP 4.8 which is also based on K8s 1.21 but will take a look at EKS as well) |
Hum good question, I was using https://github.com/k3s-io/helm-controller. The log could indicate there was a delete action on release... :/
|
I opened an issue in the helm-controller repository k3s-io/helm-controller#110. |
I am closing this as the problem seems to be with helm-controller. Let's reopen if that changes. |
Bug Report
What did you do?
I did not read the upgrade procedure (my fault) and I started an helm upgrade from 1.6.0 to 1.7.0 without first applying new crd ressources.
What did you expect to see?
Upgrade that failed.
What did you see instead? Under which circumstances?
All elastic ressources (elasticsearch, beats, kibana) were destroyed from the cluster.
Environment
1.7.0
Kubernetes information:
insert any information about your Kubernetes environment that could help us:
Logs:
The text was updated successfully, but these errors were encountered: