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

Migrate KEP-34 to new template #2471

Merged
merged 2 commits into from
Feb 9, 2021
Merged

Conversation

ehashman
Copy link
Member

@ehashman ehashman commented Feb 8, 2021

NOTE: This KEP was implemented in 1.4 and went beta in 1.11 and long predates PRR. I migrated the KEP to the new template and completed the PRR requirements as best I could. I think I put a note on the KEP for where the copy-pasting from the beta KEP ended.

The feature flag has defaulted to on for at least all current supported releases. We would like to graduate this in 1.21 and follow up on any remaining usability work in a separate KEP.

/cc @pacoxu
/sig node

xref #34

@k8s-ci-robot k8s-ci-robot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. sig/node Categorizes an issue or PR as relevant to SIG Node. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/kep Categorizes KEP tracking issues and PRs modifying the KEP directory size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Feb 8, 2021
@ehashman ehashman changed the title [WIP] Migrate KEP-34 to new template Migrate KEP-34 to new template Feb 9, 2021
@k8s-ci-robot k8s-ci-robot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Feb 9, 2021
@ehashman
Copy link
Member Author

ehashman commented Feb 9, 2021

/assign @pacoxu @johnbelamaric @derekwaynecarr

- https://github.com/kubernetes/kubernetes/issues/72593
- https://github.com/kubernetes/kubernetes/issues/74151

There may be some follow-ups required to improve usability, but I do not believe this should block graduation.
Copy link
Member Author

Choose a reason for hiding this comment

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

There was a note about unsafe sysctls and usability. Maybe we can add a graduation criteria to just document that on the website with workarounds so we can graduate this rather than worry about more code fixes in this release. @pacoxu

Copy link
Member

Choose a reason for hiding this comment

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

any scheduling enhancement we make around a node that is configured to allow unsafe sysctls would be a distinct feature.

@johnbelamaric
Copy link
Member

PRR is fine, will approve after SIG approval

Copy link
Member

@derekwaynecarr derekwaynecarr left a comment

Choose a reason for hiding this comment

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

just one change requested, which is the best kind, because it removes work for GA criteria that is no longer pertinent.


#### Graduation

* Promote `--experimental-allowed-unsafe-sysctls` kubelet flag to kubelet config api option
Copy link
Member

Choose a reason for hiding this comment

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

this flag does not exist.

it was changed to allowed-unsafe-sysctls and no further action is needed.

Copy link
Member Author

Choose a reason for hiding this comment

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

This was done, but it was done post-beta so I will keep it in GA criteria and add it into implementation history.

For some reason the issue was still open despite this having been fixed so I closed that issue.

Copy link
Member Author

Choose a reason for hiding this comment

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

- https://github.com/kubernetes/kubernetes/issues/72593
- https://github.com/kubernetes/kubernetes/issues/74151

There may be some follow-ups required to improve usability, but I do not believe this should block graduation.
Copy link
Member

Choose a reason for hiding this comment

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

any scheduling enhancement we make around a node that is configured to allow unsafe sysctls would be a distinct feature.

@derekwaynecarr
Copy link
Member

thanks for updates!

/approve
/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 9, 2021
@ehashman
Copy link
Member Author

ehashman commented Feb 9, 2021

@johnbelamaric over to you :)

@johnbelamaric
Copy link
Member

/approve

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: derekwaynecarr, ehashman, johnbelamaric

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 9, 2021
@k8s-ci-robot k8s-ci-robot merged commit 00195f2 into kubernetes:master Feb 9, 2021
@k8s-ci-robot k8s-ci-robot added this to the v1.21 milestone Feb 9, 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/kep Categorizes KEP tracking issues and PRs modifying the KEP directory lgtm "Looks good to me", indicates that a PR is ready to be merged. 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
None yet
Development

Successfully merging this pull request may close these issues.

5 participants