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

Add apiserver LoopbackClient server certificate validity period documention #46407

Open
HirazawaUi opened this issue May 16, 2024 · 4 comments · May be fixed by #49518
Open

Add apiserver LoopbackClient server certificate validity period documention #46407

HirazawaUi opened this issue May 16, 2024 · 4 comments · May be fixed by #49518
Labels
kind/feature Categorizes issue or PR as related to a new feature. language/en Issues or PRs related to English language priority/backlog Higher priority than priority/awaiting-more-evidence. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. sig/security Categorizes an issue or PR as relevant to SIG Security. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@HirazawaUi
Copy link
Contributor

This is a Feature Request

What would you like to be added

Why is this needed
We intended to add this to the documentation in 2020, but it has never been implemented
To this day, it remains invisible to most normal users (unless they read the code)

Comments
@HirazawaUi HirazawaUi added the kind/feature Categorizes issue or PR as related to a new feature. label May 16, 2024
@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label May 16, 2024
@sftim
Copy link
Contributor

sftim commented May 16, 2024

/sig api-machinery security

@k8s-ci-robot k8s-ci-robot added sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. sig/security Categorizes an issue or PR as relevant to SIG Security. labels May 16, 2024
@HirazawaUi
Copy link
Contributor Author

@sftim Can I accept this, or do we need the maintainers of sig-machinery or sig-doc to accept it?

@sftim
Copy link
Contributor

sftim commented Aug 8, 2024

Any org member can accept the issue, but if you think a relevant SIG wouldn't accept it, act with caution.

@HirazawaUi
Copy link
Contributor Author

Thanks for your explanation.
/kind feature
/language en
/triage accepted
/priority backlog

@k8s-ci-robot k8s-ci-robot added language/en Issues or PRs related to English language triage/accepted Indicates an issue or PR is ready to be actively worked on. priority/backlog Higher priority than priority/awaiting-more-evidence. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Aug 16, 2024
@HirazawaUi HirazawaUi linked a pull request Jan 21, 2025 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/feature Categorizes issue or PR as related to a new feature. language/en Issues or PRs related to English language priority/backlog Higher priority than priority/awaiting-more-evidence. sig/api-machinery Categorizes an issue or PR as relevant to SIG API Machinery. sig/security Categorizes an issue or PR as relevant to SIG Security. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add documentation for loopback certificates in kube-apiserver HirazawaUi/website
3 participants
@k8s-ci-robot @sftim @HirazawaUi