-
Notifications
You must be signed in to change notification settings - Fork 181
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
fix node discovery when nodes are not upgraded to v2.5.0 #1971
fix node discovery when nodes are not upgraded to v2.5.0 #1971
Conversation
da0dd70 to
a7c5d08
Compare
a7c5d08 to
1c77bc9
Compare
|
@chethanv28 @shalini-b I have addressed your review comments and also performed e2e upgrade validation for this PR. |
|
/approve |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/approve
/lgtm
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: chethanv28, divyenpatel, shalini-b The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
What this PR does / why we need it:
This PR helps fix node discovery when nodes are not upgraded to use v2.5.0 release of the driver, but CSI controller is upgraded to use v2.5.0
This is happening on TKGi platform during upgrade. After upgrading master node to use v2.5.0 bits, node discovery is failing as worker nodes are not yet upgraded and still have Node name as Node ID in the CSINodes object. For this case, we need to fall back and discover node using the ProviderID set on the Node object.
This PR is needed along with #1966
Testing done:
TKGI team has validated upgrading CSI driver with this change.
Special notes for your reviewer:
Release note: