feat: add GKE instance template metadata resolver to remove conflict label in karpenter. #34
Conversation
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
|
Thanks to your contribution, the maintainers will review it as soon as they can! |
|
The release note is either empty or incomplete, please consider: |
jwcesign
reviewed
Apr 30, 2025
…label in karpenter. Signed-off-by: Asklv <[email protected]>
IRONICBo
force-pushed
the
feat/support-metadata-parser
branch
from
d2f1988 to
4189045
Compare
19 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 type of PR is this?
/kind feature
What this PR does / why we need it:
Refer to the GCP Karpenter manual. We need to remove some predefined labels from the metadata.
Ref: https://docs.google.com/document/u/0/d/1FbWWIGn5soHHnRPRxnIxuninW4s64nFuYxjtOJPKXxg/mobilebasic
cc @jwcesign
Which issue(s) this PR fixes:
Fixes #16
Special notes for your reviewer:
Does this PR introduce a user-facing change?