[stub] add supervisor API that can generate kubeconfig for multiple clusters
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 739
- Forks
- 85
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 1
Description
If the supervisor had an API that could "register" workload clusters (ex: we could have a controller that syncs cluster API cluster objects into the supervisor namespace as "supervisor workload clusters"), then we could generate a kubeconfig that included all clusters to allow for more convenient access. Variations on this API include getting a kubeconfig for:
- A particular cluster
- "My" clusters
- All clusters "I" have access to
- All clusters in a federation domain
- All clusters
Related to #750
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named in the issue. Start by reviewing related issue #750 and the supervisor API context, then define which cluster-registration and kubeconfig access scopes are required; done means an agreed API design covering the listed cluster-selection variations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- api, authentication
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100