kubernetes-sigs
Generic clusterctl credential management workflow
Holding issue for more commentary in 2021 :)
User Story
The credentials I need for the initial creation of a Cluster API management cluster isn't the same as the one the management cluster needs when it becomes self-managed.
Detailed Description
Discussion in https://docs.google.com/document/d/1a1G0xtZYUmLdTKmGCNbt2V7_90N-qsFEeilplE16Zo0/edit#heading=h.oskd5jj19v2m
[A clear and concise description of what you want to happen.]
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
/kind feature
@wfernandes ^^ given this could be relevant to the management cluster operator work
/milestone v0.4.0 /area clusterctl /priority important-soon
@fabriziopandini Yup. This was created and is linked in the comments on the CAEP. Reference https://github.com/kubernetes-sigs/cluster-api/pull/3833/files#r540576353
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-contributor-experience at kubernetes/community. /lifecycle stale
/triage accept This will probably require a small proposal or some more details to make it actionable
@fabriziopandini: The label(s) triage/accept cannot be applied, because the repository doesn't have them.
In response to this:
/triage accept This will probably require a small proposal or some more details to make it actionable
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.
This issue is labeled with priority/important-soon but has not been updated in over 90 days, and should be re-triaged.
Important-soon issues must be staffed and worked on either currently, or very soon, ideally in time for the next release.
You can:
- Confirm that this issue is still relevant with
/triage accepted(org members only) - Deprioritize it with
/priority important-longtermor/priority backlog - Close this issue with
/close
For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/
/remove-triage accepted
This issue is labeled with priority/important-soon but has not been updated in over 90 days, and should be re-triaged.
Important-soon issues must be staffed and worked on either currently, or very soon, ideally in time for the next release.
You can:
- Confirm that this issue is still relevant with
/triage accepted(org members only) - Deprioritize it with
/priority important-longtermor/priority backlog - Close this issue with
/close
For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/
/remove-triage accepted
/close due to lack of activity. let's hope people interested in working in this area can restart this discussion soon
@fabriziopandini: Closing this issue.
In response to this:
/close due to lack of activity. let's hope people interested in working in this area can restart this discussion soon
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.