Open
Conversation
ibrokethecloud
force-pushed
the
mutating-webhook-implementation
branch
from
14451c8 to
1f270aa
Compare
mutating webhook in seeder. The webhook extracts userinfo from the authentication info and labels the same in cluster object. The inventory and cluster controllers then ensure that this info is synced to the associated inventory object when a cluster is created/updated and cleaned from inventory when cluster is deleted Signed-off-by: Gaurav Mehta <gaurav.mehta@suse.com> fix up linter errors Signed-off-by: Gaurav Mehta <gaurav.mehta@suse.com>
ibrokethecloud
force-pushed
the
mutating-webhook-implementation
branch
from
1f270aa to
9841d7e
Compare
FrankYang0529
approved these changes
Oct 29, 2025
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.
PR helps better tracking of inventory and cluster resources by adding a mutating webhook in seeder. The webhook extracts userinfo from the authentication info and labels the same in cluster object.
The inventory and cluster controllers then ensure that this info is synced to the associated inventory object when a cluster is created/updated and cleaned from inventory when cluster is deleted
Related issue: harvester/harvester#7949