🌱 Don't always backfill VM Status.Zone from label#1406
Merged
bryanv merged 1 commit intovmware-tanzu:mainfrom Apr 17, 2026
Merged
Conversation
akutz
approved these changes
Apr 13, 2026
Collaborator
akutz
left a comment
akutz
left a comment
There was a problem hiding this comment.
Approved, but I would ask you to please add some in-line comments in update_status.go that reflect the same messaging in the PR description. That way future folks will know the reason for this behavior. Thanks!
When either is unset, or they have different values, lookup the VM's zone and assign the zone to the label and status. To avoid a lookup if both the label and status are set to the same value, we'll just trust what is there.
bryanv
force-pushed
the
bryanv/dont-always-backfill-zone-status-from-label
branch
from
e787efe to
9c624d9
Compare
Minimum allowed line rate is |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do, and why is it needed?
When either is unset, or they have different values, lookup the VM's zone and assign the zone to the label and status. To avoid a lookup if both the label and status are set to the same value, we'll just trust what is there.
The label value is protected by the validation webhook for non privileged users, but if the label does happen to get changed - like by kube-admin - relook the correct zone.
Which issue(s) is/are addressed by this PR? (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)format, will close the issue(s) when PR gets merged):Fixes #
Are there any special notes for your reviewer:
Please add a release note if necessary: