-
Notifications
You must be signed in to change notification settings - Fork 14.6k
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
New annotations “kubectl.kubernetes.io/default-container” #27095
Conversation
Deploy preview for kubernetes-io-vnext-staging processing. Building with commit 4c51305 https://app.netlify.com/sites/kubernetes-io-vnext-staging/deploys/605439eec6d29e0008c11441 |
|
||
Example: `kubectl.kubernetes.io/default-container:container1` | ||
|
||
If a Pod has the annotation `kubectl.kubernetes.io/default-container`, consumers (CLI, operators) know which is the default container. For example, `kubectl logs` or `kubectl exec` without `-c` or `--container` flag will use this default container. |
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.
- We're listing this in the wrong place (under a heading “The taints listed below are always used on Nodes”)
- We should explicitly say that the value of the annotation is the container name that is default for this Pod.
/sig cli |
/assign |
Co-authored-by: Tim Bannister <tim@scalefactory.com>
LGTM (would like someone else to /lgtm) |
[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 |
/lgtm From sig-cli perspective Thank you @pacoxu ! |
LGTM label has been added. Git tree hash: 2a157ec136317edb66182d2cb813c8e422321c8c
|
kubernetes/enhancements#2227 (comment)
It is implemented in 1.21