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

Access runtime cluster #136

Open
petersutter opened this issue Mar 9, 2022 · 1 comment
Open

Access runtime cluster #136

petersutter opened this issue Mar 9, 2022 · 1 comment
Labels
component/gardenctl Gardener CLI kind/enhancement Enhancement, improvement, extension lifecycle/rotten Nobody worked on this for 12 months (final aging stage)

Comments

@petersutter
Copy link
Contributor

What would you like to be added:
It should be possible to access the runtime cluster using gardenctl

Why is this needed:

@petersutter petersutter added component/gardenctl Gardener CLI kind/enhancement Enhancement, improvement, extension labels Mar 9, 2022
@petersutter
Copy link
Contributor Author

proposals for obtaining the runtime cluster kubeconfig:
a) Similar to the <seedname>.login secret for seeds that contain the kubeconfig (usually with oidc configuration), a similar approach could be done for the runtime cluster. There is a secret for the runtime cluster(s), identified by label.
b) Similar to the garden cluster kubeconfig, the user has to obtain the runtime cluster kubeconfig and the user will add it to the gardenctl configuration

@gardener-robot gardener-robot added the lifecycle/stale Nobody worked on this for 6 months (will further age) label Sep 25, 2022
@gardener-robot gardener-robot added lifecycle/rotten Nobody worked on this for 12 months (final aging stage) and removed lifecycle/stale Nobody worked on this for 6 months (will further age) labels Jun 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/gardenctl Gardener CLI kind/enhancement Enhancement, improvement, extension lifecycle/rotten Nobody worked on this for 12 months (final aging stage)
Projects
None yet
Development

No branches or pull requests

2 participants