Skip to content
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 RunAsGroup to GA #94641

Merged
merged 1 commit into from Feb 19, 2021
Merged

Promote RunAsGroup to GA #94641

merged 1 commit into from Feb 19, 2021

Conversation

krmayankk
Copy link

/kind feature

What this PR does / why we need it:

promote this feature to GA for 1.20 kubernetes/enhancements#213
API is unchanged

Which issue(s) this PR fixes:
Fixes #kubernetes/enhancements#213

Special notes for your reviewer:

The `RunAsGroup` feature has been promoted to GA in this release.

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

@k8s-ci-robot k8s-ci-robot added kind/feature Categorizes issue or PR as related to a new feature. release-note Denotes a PR that will be considered when it comes time to generate release notes. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. needs-priority Indicates a PR lacks a `priority/foo` label and requires one. labels Sep 9, 2020
@krmayankk
Copy link
Author

/sig auth
/sig node

@k8s-ci-robot k8s-ci-robot added sig/auth Categorizes an issue or PR as relevant to SIG Auth. sig/node Categorizes an issue or PR as relevant to SIG Node. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Sep 9, 2020
@@ -700,7 +700,7 @@ var defaultKubernetesFeatureGates = map[featuregate.Feature]featuregate.FeatureS
CSIMigrationAzureFileComplete: {Default: false, PreRelease: featuregate.Alpha},
CSIMigrationvSphere: {Default: false, PreRelease: featuregate.Beta},
CSIMigrationvSphereComplete: {Default: false, PreRelease: featuregate.Beta},
RunAsGroup: {Default: true, PreRelease: featuregate.Beta},
RunAsGroup: {Default: true, PreRelease: featuregate.GA},
Copy link
Member

@liggitt liggitt Sep 9, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

when moving features to GA, we should:

  1. set LockToDefault: true and add a comment tracking removal in 2 releases (1.22 in this case)
  2. remove checks for .Enabled(features.RunAsGroup) (since it is locked to true)
  3. ensure API docs no longer indicate it is a beta feature (I think this is already done for this field)
  4. ensure e2e test coverage exists

@@ -249,7 +249,7 @@ const (
CRIContainerLogRotation featuregate.Feature = "CRIContainerLogRotation"

// owner: @krmayankk
// beta: v1.14
// ga: v1.20
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

leave the beta line as-is to make it easy to see the history, and add the GA line

@SergeyKanzhelev
Copy link
Member

/cc @mrunalp

(Mrunal was interested to help with this in this doc: https://docs.google.com/document/d/1-NNfuFMh246_ujQpYBCldLQ9hmqEbukaa79Xe1WGwdQ/edit#)

@k8s-ci-robot k8s-ci-robot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Sep 11, 2020
@mrunalp
Copy link
Contributor

mrunalp commented Sep 22, 2020

👍

@SergeyKanzhelev
Copy link
Member

@krmayankk as part of the GA process, can you please also help with the following:

  1. Convert KEP into the new format with the kep.yaml file (example here: Runtime class GA enhancements#2071)
  2. Request release managers to add milestone 1.21 to the KEP issue so it will be tracked by release team
  3. Add notes to the description of this PR confirming that the graduation requirements were met (you may decide to accumulate results as a do like this: https://docs.google.com/document/d/17nROj6ayPsUpx09mhLrzOkRLgo-8sn6Vgfyy-gmyuo4/edit or any other alternative way like a list of PRs confirming that the graduation criteria was met).

LMK if you need some help with these. Thank you!

@dims dims removed their request for review January 4, 2021 19:31
@krmayankk
Copy link
Author

@krmayankk as part of the GA process, can you please also help with the following:

  1. Convert KEP into the new format with the kep.yaml file (example here: kubernetes/enhancements#2071)
  2. Request release managers to add milestone 1.21 to the KEP issue so it will be tracked by release team
  3. Add notes to the description of this PR confirming that the graduation requirements were met (you may decide to accumulate results as a do like this: https://docs.google.com/document/d/17nROj6ayPsUpx09mhLrzOkRLgo-8sn6Vgfyy-gmyuo4/edit or any other alternative way like a list of PRs confirming that the graduation criteria was met).

LMK if you need some help with these. Thank you!

thanks will do

@krmayankk krmayankk force-pushed the runasg branch 2 times, most recently from 86845d8 to eec6e4f Compare January 22, 2021 08:23
@liggitt
Copy link
Member

liggitt commented Jan 22, 2021

is there an e2e test for this that should be promoted to a (Linux-only?) conformance test as part of this?

@krmayankk
Copy link
Author

krmayankk commented Jan 27, 2021

is there an e2e test for this that should be promoted to a (Linux-only?) conformance test as part of this?

i see these two e2e tests which are Linux-only and agree, they shouuld be part of conformance.
https://github.com/kubernetes/kubernetes/blob/master/test/e2e/node/security_context.go#L89
https://github.com/kubernetes/kubernetes/blob/master/test/e2e/node/security_context.go#L118

How do you make a test part of conformance @liggitt ?

@krmayankk
Copy link
Author

/test pull-kubernetes-e2e-gce-ubuntu-containerd

@krmayankk krmayankk force-pushed the runasg branch 2 times, most recently from 7c692e1 to cef8ff4 Compare January 31, 2021 20:45
@krmayankk
Copy link
Author

krmayankk commented Feb 1, 2021

is there an e2e test for this that should be promoted to a (Linux-only?) conformance test as part of this?

i see these two e2e tests which are Linux-only and agree, they shouuld be part of conformance.
https://github.com/kubernetes/kubernetes/blob/master/test/e2e/node/security_context.go#L89
https://github.com/kubernetes/kubernetes/blob/master/test/e2e/node/security_context.go#L118

How do you make a test part of conformance @liggitt ?

opened a PR to make RunAsGroup part of Conformance @liggitt @tallclair @BenTheElder FYI

#98645

@krmayankk
Copy link
Author

the kep with prr just merged kubernetes/enhancements#1974 , can you take another look @liggitt @tallclair and tell me what else is needed. Also i have opened a PR for making these tests part of conformance, which will merge after this gets in

@kikisdeliveryservice kikisdeliveryservice moved this from Waiting on Author to Needs Reviewer in SIG Node PR Triage Feb 11, 2021
@@ -208,7 +208,8 @@ const (
CRIContainerLogRotation featuregate.Feature = "CRIContainerLogRotation"

// owner: @krmayankk
// beta: v1.14
// beta: v1.14
// ga: v1.22
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we get this in v1.21?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the KEP is actually assigned to 1.21: kubernetes/enhancements#213

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

correct, do i just need to fix this item here to say ga: 1.21 ? Who owns reviewing this ?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, it should say 1.21. Any feature approver can review this file.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed

@@ -51,11 +48,9 @@ func (f *simpleStrategyFactory) CreateStrategies(psp *policy.PodSecurityPolicy,
}

var groupStrat group.GroupStrategy
if utilfeature.DefaultFeatureGate.Enabled(features.RunAsGroup) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't we keep this until the feature flag is removed in 1.22?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is example shows that it is not needed: #94140 Flag stays to make sure kubelet starts with this flag set

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So no action required from me right ?

@dims
Copy link
Member

dims commented Feb 19, 2021

/retest

@dims
Copy link
Member

dims commented Feb 19, 2021

/approve

Copy link
Member

@ehashman ehashman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Feb 19, 2021
@ehashman
Copy link
Member

/retest

@ehashman ehashman moved this from Needs Reviewer to Needs Approver in SIG Node PR Triage Feb 19, 2021
@liggitt
Copy link
Member

liggitt commented Feb 19, 2021

/approve

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dims, krmayankk, liggitt

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 19, 2021
@k8s-ci-robot k8s-ci-robot merged commit 4d75279 into kubernetes:master Feb 19, 2021
SIG Node PR Triage automation moved this from Needs Approver to Done Feb 19, 2021
@k8s-ci-robot k8s-ci-robot added this to the v1.21 milestone Feb 19, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/feature Categorizes issue or PR as related to a new feature. lgtm "Looks good to me", indicates that a PR is ready to be merged. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. release-note Denotes a PR that will be considered when it comes time to generate release notes. sig/auth Categorizes an issue or PR as relevant to SIG Auth. sig/node Categorizes an issue or PR as relevant to SIG Node. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
Development

Successfully merging this pull request may close these issues.

None yet

8 participants