Dynamic Authentication Config

[enj]

Enhancement Description

• One-line enhancement description: Dynamic Authentication Config
• Kubernetes Enhancement Proposal: Dynamic Authentication Config #1689
• Primary contact: @enj
• Responsible SIGs: sig-auth
• Enhancement target:
  • Alpha release target (1.19)
  • Beta release target (1.20)
  • Stable release target (1.21)

[enj]

/sig auth

[harshanarayana]

Hey there @enj -- 1.19 Enhancements shadow here. I wanted to check in and see if you think this Enhancement will be graduating in 1.19?

In order to have this part of the release:

1. The KEP PR must be merged in an implementable state
2. The KEP must have test plans
3. The KEP must have graduation criteria.

The current release schedule is:

• Monday, April 13: Week 1 - Release cycle begins
• Tuesday, May 19: Week 6 - Enhancements Freeze
• Thursday, June 25: Week 11 - Code Freeze
• Thursday, July 9: Week 14 - Docs must be completed and reviewed
• Tuesday, August 4: Week 17 - Kubernetes v1.19.0 released

If you do, I'll add it to the 1.19 tracking sheet (http://bit.ly/k8s-1-19-enhancements). Once coding begins please list all relevant k/k PRs in this issue so they can be tracked properly. 👍

Thanks!

[enj]

@harshanarayana the KEP is still provisional. For v1.19, at most, the KEP may be marked implementable and have an initial alpha implementation in k/k.

[harshanarayana]

Hey @enj thanks for following up.. I've updated the tracking sheets accordingly 👍

[palnabarun]

/stage alpha
/milestone v1.19

[harshanarayana]

Hey @enj, member of Enhancements team for the v1.19 here with a quick update.

PR #1620 was merged recently, adding production readiness review questions to the KEP template. We are not making it mandatory for the 1.19 release cycle, but it would be great if the PRR questionnaire is filled since the KEP is still in flight.

[msedzins]

Hi @enj ,

Enhancement shadow for the v1.19 release cycle here. Just following up on my earlier update to inform you of the
upcoming Enhancement Freeze scheduled on Tuesday, May 19.

I noticed that the KEP #1689 is still in flight. As per the requirements, the KEP should be merged and implementable for it to be
considered for the release v1.19.

I would really appreciate if you can get the KEP merged in-time for the Enhancement freeze. Please feel free to reach out in case if you need any more information.
Thx!

[palnabarun]

@enj -- Unfortunately the deadline for the 1.19 Enhancement freeze has passed. I see that the KEP PR is still not merged.

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.

[palnabarun]

/milestone clear

[liggitt]

closing per #1689 (comment)

/close

[k8s-ci-robot]

@liggitt: Closing this issue.

In response to this:

closing per #1689 (comment)

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.