-
Notifications
You must be signed in to change notification settings - Fork 14.4k
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
Register Annotation resource.kubernetes.io/pod-claim-name #47093
Conversation
/assign |
✅ Pull request preview available for checkingBuilt without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
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 think these suggestions are correct, but I also recommend a tech review.
|
||
Example: `resource.kubernetes.io/pod-claim-name: "my-pod-claim"` | ||
|
||
Used on: Pod |
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.
Used on: Pod | |
Used on: ResourceClaim |
@sftim I've added the suggestion, can you please review thanks! |
/sig node |
Hello @kubernetes/sig-node-leads,
We'd like to have a technical review of this PR. |
Hello @kubernetes/sig-node-leads can someone review this PR that will be really helpful |
Its value corresponds to the name of the resource claim in the `.spec` of any Pod(s) for which the ResourceClaim was created. | ||
This annotation is an internal implementation detail of [dynamic resource allocation](/docs/concepts/scheduling-eviction/dynamic-resource-allocation/). | ||
You should not need to read or modify the value of this annotation. | ||
|
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.
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 is indeed intentional.
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.
OK, but per #47044 we don't have a way to register annotations without also documenting them.
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.
(adding such a mechanism is welcome, and it's not actually a huge amount of work, but it'd be bigger than this PR)
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.
You can document them here. It just makes less sense to also document it in the public types.go as a const string
.
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.
/lgtm
LGTM label has been added. Git tree hash: 3ae76c08abf449a9691b42d819de0d959b1bd8d7
|
/assign @sftim |
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.
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sftim The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Closes #47044
Problem: The annotation
resource.kubernetes.io/pod-claim-name
is unregistered, but used in Kubernetes code.Changes: Registered the annotation, by mentioning it in Well-Known Labels, Annotations and Taints.
Additional Information:
Required for kubernetes/enhancements#3063