-
Notifications
You must be signed in to change notification settings - Fork 7.8k
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
Use the zone from the metadata for creating locality #53821
Use the zone from the metadata for creating locality #53821
Conversation
/test release-notes |
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.
I assume this fixes #50379, right?
564ef7a
to
a3f346f
Compare
Change-Id: I27f1b699f7ea464eb43993eb7870ee15f7ffc8ad
a3f346f
to
52f395e
Compare
Change-Id: I63c0f955d6ed3a6051e34baa05ef9f05bbd46001
Actually, it was not, but I realized that it is great to solve the issue together. So, we are now using zone of Pod, not the cluster's zone. |
/retest |
Change-Id: Iac06b870add610464da13bc92d54817b8f5753bb
Implementation looks fine to me except the two comments above. |
Change-Id: Ibc72d0dc3800fca7de781edb3858e454fdb9716b
Change-Id: I5e38ccdc61621d933e595bfab9a45a0bede1bc32
/retest |
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.
This regresses a major chunk of work done on Google's mesh to drop the dependency on the metadata server which was the result of a massive list of issues. Given this only impacts that product and not OSS, though, I suppose this looks good..
* Use the zone from the metadata Change-Id: I27f1b699f7ea464eb43993eb7870ee15f7ffc8ad * Fix the test cases. Change-Id: I63c0f955d6ed3a6051e34baa05ef9f05bbd46001 * Reduce the timeout to 3 sec Change-Id: Iac06b870add610464da13bc92d54817b8f5753bb * Reflect comments and add GCP_ZONE env var for overriding Change-Id: Ibc72d0dc3800fca7de781edb3858e454fdb9716b * Fix the failure in the unit test Change-Id: I5e38ccdc61621d933e595bfab9a45a0bede1bc32
Current implementation is assuming that the cluster location is "zone" when creating Locality for GCP platform.
However, for the GKE regional cluster, it is not true.
Therefore, this PR proposes to use "metadata" server to get the zone, if the cluster location is not zonal.
Change-Id: I27f1b699f7ea464eb43993eb7870ee15f7ffc8ad