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
[IMPROVEMENT] Remove privilege requirement from lifecycle jobs #5862
Comments
@mantissahz Try to fix this together with upgrade enforcement. Thanks. cc @PhanLe1010 |
Pre Ready-For-Testing Checklist
|
@mantissahz need to check if we need to update the doc. |
Hi @mantissahz , From test steps, I can install/uninstall Longhorn by
pre upgrade pod log
|
@chriscchien |
Verified in longhorn master (longhorn-manager
|
@chriscchien can we test failed case? like 1.3 to 1.5/master? also after it failed, we should be able to recover it by following #5131 (comment). |
Hi @mantissahz , I tried upgrade Longhorn from v1.3.x to master-head by But I saw below deployment components had upgraded to newer version as the setting in master-head manifest
I can recover them by apply v1.3.x manifest again, not sure if this is the correct behavior, thank you. |
@chriscchien |
Reopened first to let QA finish the complete testing before closing this issue. @mantissahz Do we have the doc for upgrade enforcement? The issue has |
Hi @mantissahz, I can do
But when I try downgrade form master to v1.3.x by |
Verify pass with longhorn-manager (master
Downgrade failure case can see below log and longhorn-manager pod kept in
May need test again after code of cc @innobead , @mantissahz |
@mantissahz What else we need to update/fix? I assumed all changes have been merged, right? |
Yes, there is nothing needed to fix or update. |
After discussed with @mantissahz , we can follow test result here and close this ticket, thank you. |
But I just walked through the post-upgrade and uninstall job. They are just doing operations against kubeAPI. Not sure why we need them to be privileged
Originally posted by @PhanLe1010 in #5567 (comment)
The text was updated successfully, but these errors were encountered: