-
Notifications
You must be signed in to change notification settings - Fork 40.9k
Promote feature OrderedNamespaceDeletion to GA. #131514
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
Conversation
test/e2e/apimachinery/namespace.go
Outdated
@@ -481,7 +480,7 @@ var _ = SIGDescribe("OrderedNamespaceDeletion", func() { | |||
f := framework.NewDefaultFramework("namespacedeletion") | |||
f.NamespacePodSecurityLevel = admissionapi.LevelBaseline | |||
|
|||
f.It("namespace deletion should delete pod first", feature.OrderedNamespaceDeletion, framework.WithFeatureGate(features.OrderedNamespaceDeletion), func(ctx context.Context) { |
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'll keep the WithFeatureGate
because it provides information but does not disable running the test in most CI (unless the feature were off-by-default)
but we should drop the e2e feature
https://groups.google.com/a/kubernetes.io/g/dev/c/uVga86nJDuI
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.
Thank you for the review. Updated
#131518 merged |
/assign @jpbetz |
/triage accepted |
Quick request: Can we include a summary of how the GA criteria has been achieved, or if we're not targeting the criteria in the KEP, can we update the KEP to match our target criteria? |
The KEP been updated in kubernetes/enhancements#5191 and ready to merge. Thanks |
/approve cc @Jefftree to double check for emu. version adherence |
For emu version, main thing is checking for disablement tests (in unit/integration) with a previous non locked version. I noticed there aren't any disablement tests with this feature, I'm assuming this is because the existing behavior is already covered by tests and this is intentional? Otherwise emulation version/feature gate changes lgtm. |
I think we want to get the testing going for this so we can aim to add to conformance as well? If we can't merge the rest of this soon, I'd request splitting out the Right now we're not running this test. |
@jeffrey Thanks for the review. Yes the existing behavior is covered by test and since it's addressing security concern we'd love to encourage all users to follow the current behavior^^ |
/lgtm |
LGTM label has been added. Git tree hash: f4b89311e1fdd0db383fdf8cd4c5ef2312d8c43b
|
needs rebase |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cici37, jpbetz 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 |
/unhold |
/lgtm |
LGTM label has been added. Git tree hash: 46994f27737e85de496628dfeb3d507d61a1b88b
|
What type of PR is this?
/kind feature
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: