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

Provide OIDC discovery for service account token issuer #1393

Closed
12 tasks done
mtaufen opened this issue Dec 5, 2019 · 72 comments
Closed
12 tasks done

Provide OIDC discovery for service account token issuer #1393

mtaufen opened this issue Dec 5, 2019 · 72 comments
Assignees
Labels
kind/api-change Categorizes issue or PR as related to adding, removing, or otherwise changing an API sig/auth Categorizes an issue or PR as relevant to SIG Auth. stage/stable Denotes an issue tracking an enhancement targeted for Stable/GA status tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team
Projects
Milestone

Comments

@mtaufen
Copy link
Contributor

mtaufen commented Dec 5, 2019

Enhancement Description

@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Dec 5, 2019
@mtaufen
Copy link
Contributor Author

mtaufen commented Dec 5, 2019

/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 Dec 5, 2019
@mtaufen
Copy link
Contributor Author

mtaufen commented Dec 5, 2019

/assign @mtaufen

@mtaufen
Copy link
Contributor Author

mtaufen commented Dec 5, 2019

/milestone 1.18

@k8s-ci-robot
Copy link
Contributor

k8s-ci-robot commented Dec 5, 2019

@mtaufen: You must be a member of the kubernetes/milestone-maintainers GitHub team to set the milestone. If you believe you should be able to issue the /milestone command, please contact your and have them propose you as an additional delegate for this responsibility.

In response to this:

/milestone 1.18

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.

@mrbobbytables mrbobbytables added the tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team label Dec 10, 2019
@helayoty
Copy link
Member

helayoty commented Jan 15, 2020

Hey there @mtaufen -- 1.18 Enhancements shadow here. I wanted to check in and see if you think this Enhancement will be graduating to alpha in 1.18 or having a major change in its current level?

The current release schedule is:

Tuesday, January 28th EOD PST - Enhancements Freeze
Thursday, March 5th, EOD PST - Code Freeze
Monday, March 16th - Docs must be completed and reviewed
Tuesday, March 24th - Kubernetes 1.18.0 Released

To be included in the release, this enhancement must have a merged KEP in the implementable status.

The KEP must also have graduation criteria and a Test Plan defined.

If you would like to include this enhancement, once coding begins please list all relevant k/k PRs in this issue so they can be tracked properly. 👍

Thanks!

@mtaufen
Copy link
Contributor Author

mtaufen commented Jan 16, 2020

@mtaufen
Copy link
Contributor Author

mtaufen commented Jan 16, 2020

@helayoty
Copy link
Member

helayoty commented Jan 16, 2020

@mtaufen Thanks for the update. I'd appreciate having the updated KEP in an implementable status along with all relevant k/k PRs in the issue.

@helayoty
Copy link
Member

helayoty commented Jan 16, 2020

/milestone v1.18

@k8s-ci-robot k8s-ci-robot added this to the v1.18 milestone Jan 16, 2020
@helayoty helayoty added tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team and removed tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team labels Jan 16, 2020
@mtaufen
Copy link
Contributor Author

mtaufen commented Jan 29, 2020

KEP is merged as implementable as of yesterday.

@liggitt liggitt added the kind/api-change Categorizes issue or PR as related to adding, removing, or otherwise changing an API label Jan 30, 2020
@VineethReddy02
Copy link

VineethReddy02 commented Feb 5, 2020

Hello, @mtaufen, I'm 1.18 docs lead.
Does this enhancement work planned for 1.18 require any new docs (or modifications to existing docs)? If not, can you please update the 1.18 Enhancement Tracker Sheet (or let me know and I'll do so)
If so, just a friendly reminder we're looking for a PR against k/website (branch dev-1.18) due by Friday, Feb 28th, it can just be a placeholder PR at this time. Let me know if you have any questions!

@mtaufen
Copy link
Contributor Author

mtaufen commented Feb 6, 2020

@VineethReddy02
Copy link

VineethReddy02 commented Feb 21, 2020

Hello @mtaufen
We are close to the docs placeholder PR deadline i.e less than week left for docs placeholder PR against the dev-1.18 branch. Having a placeholder PR in place will definitely help us in tracking enhnacements much better.

Thanks! :)

@jeremyrickard
Copy link
Contributor

jeremyrickard commented Feb 24, 2020

@mtaufen

We are getting pretty close to the code freeze deadline of 05 March 2020.

Can you please link to any k/k PRs for us so we can better track this?

@mtaufen
Copy link
Contributor Author

mtaufen commented Feb 24, 2020

@jeremyrickard all associated PRs are linked in the issue description.

@VineethReddy02 I plan to have a placeholder PR up by the end of this week, thanks!

@VineethReddy02
Copy link

VineethReddy02 commented Feb 24, 2020

Hi @mtaufen
The deadline for the placeholder PR is 28th Feb we are close to the deadline. It would be great if we can have placeholder PR in place sooner than later.

@mtaufen
Copy link
Contributor Author

mtaufen commented Feb 26, 2020

Docs PR: kubernetes/website#19328

@helayoty
Copy link
Member

helayoty commented Mar 4, 2020

Hi @mtaufen We're only a few days out from code freeze now. It does not look like your PR has merged yet, are you still feeling like you're on track for code freeze for this enhancement? Do you want to defer this to 1.19 based on the reviewer bandwidth? Or try and make a push?

@helayoty helayoty 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 Mar 5, 2020
@helayoty
Copy link
Member

helayoty commented Mar 5, 2020

/milestone clear

@annajung annajung added the tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team label Jan 13, 2021
@liggitt
Copy link
Member

liggitt commented Feb 1, 2021

added to tracking spreadsheet for 1.21

@annajung annajung added stage/stable Denotes an issue tracking an enhancement targeted for Stable/GA status tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team and removed stage/beta Denotes an issue tracking an enhancement targeted for Beta status tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team labels Feb 3, 2021
@mvortizr
Copy link

mvortizr commented Feb 20, 2021

/milestone 1.21

@k8s-ci-robot
Copy link
Contributor

k8s-ci-robot commented Feb 20, 2021

@mvortizr: You must be a member of the kubernetes/milestone-maintainers GitHub team to set the milestone. If you believe you should be able to issue the /milestone command, please contact your and have them propose you as an additional delegate for this responsibility.

In response to this:

/milestone 1.21

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.

@mvortizr
Copy link

mvortizr commented Feb 20, 2021

/assign

@arunmk
Copy link

arunmk commented Feb 20, 2021

Hi @mtaufen @mvortizr,

Since your Enhancement is scheduled to be in 1.21, please keep in mind the important upcoming dates:

  • Tuesday, March 9th: Week 9 - Code Freeze
  • Tuesday, March 16th: Week 10 - Docs Placeholder PR deadline
    • If this enhancement requires new docs or modification to existing docs, please follow the steps in the Open a placeholder PR doc to open a PR against k/website repo.

As a reminder, please link all of your k/k PR(s) and k/website PR(s) to this issue so we can track them.

Thanks!

@mtaufen
Copy link
Contributor Author

mtaufen commented Feb 21, 2021

@arunmk thanks for reaching out. All work is linked and complete except for the pending docs PR (linked above).

@mtaufen
Copy link
Contributor Author

mtaufen commented Feb 25, 2021

All done 😄

@arunmk
Copy link

arunmk commented Feb 26, 2021

Thank you @mtaufen

@arunmk
Copy link

arunmk commented Mar 2, 2021

Hi @mtaufen,

Enhancements team is currently tracking the following PRs

Since these PRs are merged, can we mark this enhancement complete for code freeze or do you have other PR(s) that are being worked on as part of the release?

Thanks

@annajung
Copy link
Member

annajung commented Apr 8, 2021

Hi @mtaufen 1.21 Enhancement Lead here.

Can you update the kep.yaml to reflect a status of implemented:

Once that merges, we can close out this issue.

@ritazh ritazh added this to KEP Backlog in SIG Auth Apr 9, 2021
mtaufen added a commit to mtaufen/enhancements that referenced this issue Apr 19, 2021
@mtaufen
Copy link
Contributor Author

mtaufen commented Apr 19, 2021

Thanks for the reminder: #2637

@liggitt
Copy link
Member

liggitt commented Apr 19, 2021

marked implemented

/close

@k8s-ci-robot
Copy link
Contributor

k8s-ci-robot commented Apr 19, 2021

@liggitt: Closing this issue.

In response to this:

marked implemented

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

SIG Auth automation moved this from KEP Backlog to Closed / Done Apr 19, 2021
@JamesLaverack JamesLaverack 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 Apr 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/api-change Categorizes issue or PR as related to adding, removing, or otherwise changing an API sig/auth Categorizes an issue or PR as relevant to SIG Auth. stage/stable Denotes an issue tracking an enhancement targeted for Stable/GA status tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team
Projects
SIG Auth
Closed / Done
Development

No branches or pull requests