-
Notifications
You must be signed in to change notification settings - Fork 20
feat: add tags field to lease, to allow user set metadata #622
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
Draft
bennyz
wants to merge
5
commits into
main
Choose a base branch
from
lease-tags-wt
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
aa72235
feat: add tags field to lease protobuf and CRD types
bennyz 430d296
feat: implement lease tag validation, storage, and filtering
bennyz d7e9a3c
feat: add configurable maxTags via operator LeasePolicy CR
bennyz 2fafd2e
feat: add lease tags to Python CLI, client, and MCP
bennyz 385bb2b
docs: add JEP-0012 for custom user tags on leases
bennyz File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
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
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
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
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.
🧩 Analysis chain
🏁 Script executed:
Repository: jumpstarter-dev/jumpstarter
Length of output: 10337
🏁 Script executed:
Repository: jumpstarter-dev/jumpstarter
Length of output: 53
🏁 Script executed:
Repository: jumpstarter-dev/jumpstarter
Length of output: 53
🏁 Script executed:
Repository: jumpstarter-dev/jumpstarter
Length of output: 131
🏁 Script executed:
Repository: jumpstarter-dev/jumpstarter
Length of output: 53
🏁 Script executed:
Repository: jumpstarter-dev/jumpstarter
Length of output: 7658
🏁 Script executed:
Repository: jumpstarter-dev/jumpstarter
Length of output: 53
🏁 Script executed:
Repository: jumpstarter-dev/jumpstarter
Length of output: 175
🏁 Script executed:
Repository: jumpstarter-dev/jumpstarter
Length of output: 1704
🏁 Script executed:
Repository: jumpstarter-dev/jumpstarter
Length of output: 187
🏁 Script executed:
Repository: jumpstarter-dev/jumpstarter
Length of output: 926
Add CRD-level immutability and label-rule validation for the Tags field.
The
Tagsfield is documented as immutable and label-rule constrained, but the generated CRD enforces onlymaxProperties: 10.ValidateLeaseTagsvalidates all constraints comprehensively, but it's only called from the gRPC service layer. Direct Kubernetes writes via kubectl or controllers can mutatespec.tagsor persist invalid keys/values, bypassing validation and potentially desynchronizing tags from the prefixed metadata labels used for filtering.Suggested fix
// User-defined tags for the lease. Immutable after creation. // Maximum 10 entries. Keys and values must conform to Kubernetes label rules. // +kubebuilder:validation:MaxProperties=10 + // +kubebuilder:validation:XValidation:rule="self == oldSelf",message="lease tags are immutable" Tags map[string]string `json:"tags,omitempty"`Add CEL validation rules in the generated CRD to enforce immutability and label-rule conformance for keys and values, or implement ValidateCreate/ValidateUpdate webhook methods on the Lease type.
📝 Committable suggestion
🤖 Prompt for AI Agents