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
Promote EphemeralContainers to beta #105405
Conversation
Skipping CI for Draft Pull Request. |
/triage accepted |
This PR must be rebased after #103372 merges. Draft until then. /test all |
This PR may require API review. If so, when the changes are ready, complete the pre-review checklist and request an API review. Status of requested reviews is tracked in the API Review project. |
👍 I think I've addressed all of these. @msau42 I've added a commit to allow |
I think it's fine for |
- Apply doc style guide - Specify behavior when namespace targeting isn't supported by runtime
The tags for type EphemeralContainerCommon should be kept in sync with those of type Container. Co-authored-by: Jordan Liggitt <liggitt@google.com>
Listing these explicitly makes it easier to determine whether a new Container field has been evaluated for use with ephemeral containers. This does not change the behavior of ephemeral containers.
/assign @dchen1107 |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: liggitt, verb 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 and thanks! |
What type of PR is this?
/kind feature
/sig node
/priority important-soon
What this PR does / why we need it:
This promotes KEP-277 to beta
Which issue(s) this PR fixes:
Fixes #98808
Special notes for your reviewer:
KEP Graduation Criteria:
kubectl
or akubectl
plugin)./ephemeralcontainers
validates entire PodSpec to protect against future bugsPR TODO:
ephemeralContainerStatuses
EphemeralContainerCommon
field metadata remains in sync withContainer
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: