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

kubeadm: generate a client certificate with "system:masters" in a separate file #4214

Open
neolit123 opened this issue Sep 15, 2023 · 4 comments
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature. sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle.
Milestone

Comments

@neolit123
Copy link
Member

neolit123 commented Sep 15, 2023

Enhancement Description

Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.

kubernetes/kubeadm#2414

KEP file changes:

@neolit123 neolit123 added sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. kind/feature Categorizes issue or PR as related to a new feature. labels Sep 15, 2023
@neolit123 neolit123 added this to the v1.29 milestone Sep 15, 2023
@neolit123 neolit123 self-assigned this Sep 15, 2023
@npolshakova
Copy link

Hello @neolit123, 1.29 Enhancements team here! Is this enhancement targeting 1.29? If it is, can you follow the instructions here to opt in the enhancements and make sure the lead-opted-in label is set so it can get added to the tracking board? Thanks!

@neolit123
Copy link
Member Author

Hello @neolit123, 1.29 Enhancements team here! Is this enhancement targeting 1.29? If it is, can you follow the instructions here to opt in the enhancements and make sure the lead-opted-in label is set so it can get added to the tracking board? Thanks!

hi, is it possible to not opt-in into the enhancement tracking? asking as a sig lead.

@npolshakova
Copy link

Yep, currently this enhancement is not being tracked in the 1.29 enhancements tracking project board. If that's the intention, you don't need to change anything. You've set the milestone as 1.29 so I wanted to double check you didn't intend it to be tracked for 1.29.

@neolit123
Copy link
Member Author

If that's the intention, you don't need to change anything.

yes, preferably. we do all the docs / e2e / code tracking changes ourself as kubeadm is a relatively small project.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle.
Projects
None yet
Development

No branches or pull requests

2 participants