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

Dynamic Authentication Config #1688

Closed
enj opened this issue Apr 15, 2020 · 11 comments
Closed

Dynamic Authentication Config #1688

enj opened this issue Apr 15, 2020 · 11 comments
Labels
sig/auth Categorizes an issue or PR as relevant to SIG Auth. stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team

Comments

@enj
Copy link
Member

enj commented Apr 15, 2020

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)
@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Apr 15, 2020
@enj
Copy link
Member Author

enj commented Apr 15, 2020

/sig auth

@k8s-ci-robot k8s-ci-robot added sig/auth Categorizes an issue or PR as relevant to SIG Auth. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Apr 15, 2020
@harshanarayana
Copy link

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
Copy link
Member Author

enj commented May 1, 2020

@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
Copy link

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

@palnabarun
Copy link
Member

/stage alpha
/milestone v1.19

@k8s-ci-robot k8s-ci-robot added the stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status label May 4, 2020
@k8s-ci-robot k8s-ci-robot added this to the v1.19 milestone May 4, 2020
@palnabarun palnabarun added the tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team label May 4, 2020
@harshanarayana
Copy link

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
Copy link

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
Copy link
Member

@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 palnabarun added tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team and removed tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team labels May 20, 2020
@palnabarun
Copy link
Member

/milestone clear

@k8s-ci-robot k8s-ci-robot removed this from the v1.19 milestone May 20, 2020
@liggitt
Copy link
Member

liggitt commented May 21, 2020

closing per #1689 (comment)

/close

@k8s-ci-robot
Copy link
Contributor

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
sig/auth Categorizes an issue or PR as relevant to SIG Auth. stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team
Projects
None yet
Development

No branches or pull requests

6 participants