-
Notifications
You must be signed in to change notification settings - Fork 222
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
trident-csi controller is CrashLoopBackOff on updating #508
Comments
Hello @ysakashita, It appears that when you are updating Trident Operator, you are updating the existing Trident Operator deployment with the newer Trident Operator image. The preferred workflow to update the Trident Operator (and thus Trident) is to delete the old Trident Operator |
@ntap-arorar I understood bundle.yaml way. Especially in an environment where many Kubernetes are running, It's just ideas for enhancement without uninstall operation(bundle.yaml) (Idea1): Add |
The "Recreate" strategy was added with this commit and is included in Trident 21.04.0. |
Describe the bug
When trident-operator update version, the trident-csi controller sometimes down(CrashLoopBackOff).
I believe that it is a serious bug because it cannot be automatically recovered.
Especially, this is a big problem for us, as we are managing so many Kubernetes clusters.
Environment
Provide accurate information about the environment to help us reproduce the issue.
To Reproduce
I tried to repeat over 100 times updating trident-operator from 20.10.0 to 20.10.1 using the following script.
Then the trident-csi controller was not restarted.
Expected behavior
I expect correct running the trident-csi controller after updating trident-operator.
Additional context
We guess that it works like the following steps.
Additional, we try to change the
.spec.strategy.type: Recreate
in trident-csi deployment.As a result, I think the issue doesn’t occur.
logs
The text was updated successfully, but these errors were encountered: