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.

Sign up for GitHub

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

Jump to bottom

Create a Tasks doc for Service Account Issuer Discovery #19496

Closed
mtaufen opened this issue Mar 5, 2020 · 6 comments
Closed

Create a Tasks doc for Service Account Issuer Discovery #19496

mtaufen opened this issue Mar 5, 2020 · 6 comments
Assignees
@mtaufen
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/backlog Higher priority than priority/awaiting-more-evidence.

Comments

@mtaufen
Copy link
Contributor

mtaufen commented Mar 5, 2020

This is a Feature Request

What would you like to be added
Add a Tasks doc for configuring Service Account Issuer Discovery before the feature goes to beta.

Why is this needed
To help users understand how to configure the feature correctly.

Comments
@sftim recommended we make this a beta requirement #19328 (review)

/assign @mtaufen
/cc @sftim @mikedanese
@mtaufen mtaufen mentioned this issue Mar 5, 2020
Merged
@sftim
Copy link
Contributor

sftim commented Mar 5, 2020

/cc

@sftim
Copy link
Contributor

sftim commented Mar 6, 2020

Thanks @mtaufen !

/kind feature
/priority backlog

@k8s-ci-robot k8s-ci-robot added kind/feature Categorizes issue or PR as related to a new feature. priority/backlog Higher priority than priority/awaiting-more-evidence. labels Mar 6, 2020
@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 4, 2020
@mtaufen
Copy link
Contributor Author

mtaufen commented Jun 25, 2020

/remove-lifecycle stale
/lifecycle frozen

@k8s-ci-robot k8s-ci-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jun 25, 2020
@divya-mohan0209
Copy link
Contributor

@mtaufen do we still need this issue to be open? I see this feature is stable currently and wanted to check in if we still plan on including more documentation around this?

@mtaufen
Copy link
Contributor Author

mtaufen commented Jan 19, 2023

We can close this.

@mtaufen mtaufen closed this as completed Jan 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mtaufen mtaufen

Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/backlog Higher priority than priority/awaiting-more-evidence.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@mtaufen @k8s-ci-robot @divya-mohan0209 @sftim @fejta-bot