-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Configurable Pod Process Namespace Sharing #495
Comments
/sig node |
/assign @verb |
@verb 👋 Please indicate in the 1.9 feature tracking board |
@verb Bump for docs ☝️ /cc @idvoretskyi |
@zacharysarah updated tracking, feature slips to 1.10 |
Automatic merge from submit-queue (batch tested with PRs 54230, 58100, 57861, 54752). If you want to cherry-pick this change to another branch, please follow the instructions <a href="https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md">here</a>. Add a feature flag for sharing process namespace between containers in a pod **What this PR does / why we need it**: This adds a feature flag for the feature described in kubernetes/enhancements#495. **Which issue(s) this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close the issue(s) when PR gets merged)*: Fixes # **Special notes for your reviewer**: /assign @dchen1107 **Release note**: ```release-note NONE ```
Hey, can you change the milestone for this to 1.10 so that the release team can track it properly? Thanks. |
@jberkus who, me? I don't think I can. At least, it's not listed as a bot command |
/kind feature |
This feature is on track for alpha in 1.10.
|
Feature will be included as alpha in 1.10. |
Automatic merge from submit-queue. If you want to cherry-pick this change to another branch, please follow the instructions <a href="https://github.com/kubernetes/community/blob/master/contributors/devel/cherry-picks.md">here</a>. Add node-e2e test for ShareProcessNamespace **What this PR does / why we need it**: Adds a node-e2e test for kubernetes/enhancements#495 **Which issue(s) this PR fixes** *(optional, in `fixes #<issue number>(, fixes #<issue_number>, ...)` format, will close the issue(s) when PR gets merged)*: Fixes #59554 **Special notes for your reviewer**: This requires a feature gate to be enabled in both the kubelet and API server. I'm not sure which jenkins configs need to be updated (or if these are even still used) so I just updated a pile of them. opened kubernetes/test-infra#7030 for https://github.com/kubernetes/test-infra/blob/master/jobs/config.json **Release note**: ```release-note NONE ```
@verb If so, can you please ensure the feature is up-to-date with the appropriate:
cc @idvoretskyi |
Thanks @verb! |
Hello @verb I'm one of the v1.17 docs shadows. If so, just a friendly reminder we're looking for a PR against k/website (branch dev-1.17) due by Friday, November 8th, it can just be a placeholder PR at this time. Let me know if you have any questions! |
@irvifa This will require a minor update of k/website to mark the feature as stable. I don't have a link to the tracker handy, so if you could update it I would appreciate it. Ack, will open a PR against dev-1.17 by November 8. |
Hi @verb |
kubernetes/kubernetes#84356 to promote to GA |
kubernetes/website#17192 for docs |
Hey @verb 1.17 Enhancement Shadow here! 👋 I am reaching out to check in with you to see how this enhancement is going. Thank you for providing k/k PR, I have added the following kubernetes/kubernetes#84356 in the tracking sheet. Are there any other k/k PRs that need to be tracked as well? Also, another friendly reminder that we're quickly approaching code freeze (Nov. 14th). |
@annajung Thanks for checking in. We're in good shape here. The linked k/k and k/w PRs are the only ones, and all we need is final sig-node approval. |
Hi @verb , Tomorrow is code freeze for 1.17 release cycle. It looks like the k/k PRs have not been merged. We’re flagging this enhancement as Do you think all necessary PRs will be merged by the EoD of the 14th (Thursday)? After that, only release-blocking issues and PRs will be allowed in the milestone with an exception. |
@annajung the k/k PR is in the merge pool. I think it will merge. |
The only remaining item for this feature is to finish removing the feature gate in 1.19. Enhancement leads: this feature should be excluded from 1.18 and included in 1.19. |
Hi @verb, -- 1.19 Enhancements Lead here, can you confirm if the feature gate is still scheduled to be removed in 1.19? If you do, I'll add it to the 1.19 tracking sheet (http://bit.ly/k8s-1-19-enhancements). Once the work begins please list the relevant k/k PR in this issue so it can be tracked properly. 👍 The current release schedule is:
|
/milestone clear (removing this issue from v1.17 milestone since the milestone is complete) |
@palnabarun I'm prepared to remove the feature gate, but I saw an announcement that 1.19 should avoid unnecessary backwards-incompatible changes. Could you advise on whether we should proceed with a feature gate clean up or push it to 1.20? |
Hi @verb We are encouraging SIGs to push for features this cycle which do not increase end-user complexity. If removing the feature gate breaks backward compatibility, I would suggest against removing it this cycle. However, I think discussing with the SIG would be the best way to get an answer to the question. Thanks! 👍 |
@verb -- Unfortunately, the deadline for the 1.19 Enhancement freeze has passed. For now, this is being removed from the milestone and 1.19 tracking sheet. If there is a need to get this in, please file an enhancement exception. |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale |
Looks like the PodShareProcessNamespace feature gate was removed in 1.19, anyway (#90096, @tedyu) This feature is complete. 🎉 |
Feature Description
The text was updated successfully, but these errors were encountered: