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

Pod Security Policy replacement #2579

Open
tallclair opened this issue Mar 19, 2021 · 5 comments
Open

Pod Security Policy replacement #2579

tallclair opened this issue Mar 19, 2021 · 5 comments

Comments

@tallclair
Copy link
Member

@tallclair tallclair commented Mar 19, 2021

Enhancement Description

Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.

@tallclair tallclair added this to the v1.22 milestone Mar 19, 2021
@tallclair tallclair mentioned this issue Mar 22, 2021
12 of 18 tasks complete
@tallclair tallclair changed the title Pod Isolation Policy (Pod Security Policy replacement) Pod Security Policy replacement Mar 30, 2021
@ritazh ritazh added this to KEP Backlog in SIG Auth Apr 9, 2021
@liggitt liggitt moved this from KEP Backlog to Backlog (v1.22) in SIG Auth Apr 16, 2021
@liggitt liggitt moved this from Backlog (v1.22) to KEP Backlog in SIG Auth Apr 16, 2021
@liggitt liggitt moved this from KEP Backlog to In Progress (v1.22) in SIG Auth Apr 29, 2021
@liggitt liggitt moved this from In Progress (v1.22) to In Review (v1.22) in SIG Auth Apr 29, 2021
@liggitt liggitt moved this from In Review (v1.22) to In Progress (v1.22) in SIG Auth Apr 29, 2021
@gracenng
Copy link

@gracenng gracenng commented May 9, 2021

Hi @tallclair 👋 1.22 Enhancements shadow here.

This enhancement is in good shape for 1.22, a couple minor change requests in light of Enhancement Freeze on Thursday May 13th:

  • KEP has not been merged to master
  • the "reviewers" section in kep.yaml is not filled out
  • <<[unresolved]>> in README
  • Graduation Criteria in README

Thank you!

@tallclair
Copy link
Member Author

@tallclair tallclair commented May 10, 2021

  • I'm nagging the approvers daily, and still expect to get this merged by enhancement freeze
  • Filled in reviewers
  • The only remaining unresolved sections are explicitly flagged as non-blocking for the alpha. Is it OK to leave these sections for beta, or will they cause tooling issues?
  • Filled in graduation criteria
@gracenng
Copy link

@gracenng gracenng commented May 10, 2021

Hi there, thanks for the speedy updates.

  • I talked to the team and it is okay to have unresolved sections for alpha
  • With regards to graduation criteria, the KEP template has been updated to clarify this. Apologies for the confusion.
@gracenng
Copy link

@gracenng gracenng commented May 11, 2021

Hi @tallclair 👋 1.22 Enhancements shadow here.
I just wanted to double check to see if SIG-Auth will need to do anything for this enhancement and if so, are they OK with it?
Thanks!

@liggitt
Copy link
Member

@liggitt liggitt commented May 11, 2021

yes, this is one of the top three items sig-auth is tackling this release

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
SIG Auth
In Progress (v1.22)
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
6 participants