-
Notifications
You must be signed in to change notification settings - Fork 345
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
Upgrade from 1.32.0 to 1.33.0 fails #1870
Comments
thx for reporting, I'll try to take a closer look during the week. |
I get the same error but i'm upgrading from 1.31.0 |
@ivaske did you use OLM or also just a deployment? |
@frzifus A few weeks ago i did the same with Version 1.31.0 and wanted to update now. |
@frzifus root cause for this issue, we have introduced extra match selector label in deployment of the recent build. As per the k8s doc, Deployment's label selector is immutable new selector label:
k8s doc
|
But how do you add more labels via operator sdk? Maybe we want to add more common labels in the future. I expected that a deployment is replaced. Is there an csv option to overwrite deployments? Found this in $ kubectl apply -h | grep overwrite
--overwrite=true: Automatically resolve conflicts between the modified and live configuration by using values from the modified configuration |
we could solve the issue temporarily by simply removing the label, what do you think? @jkandasa @rubenvp8510 |
@frzifus I am fine with removing the label |
I'm fine with removing the label too. |
Would like to briefly check if the problem also occurs with olm too. If not, we should extend the documentation that |
Describe the bug
I tried to upgrade from Jaeger Operator v1.32.0 to 1.33.0 and it failed.
To Reproduce
Steps to reproduce the behavior:
This gave me:
Expected behavior
The operator should upgrade to 1.33.0
The text was updated successfully, but these errors were encountered: