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

Get kubeconfig path of current target #122

Closed
petersutter opened this issue Feb 22, 2022 · 2 comments
Closed

Get kubeconfig path of current target #122

petersutter opened this issue Feb 22, 2022 · 2 comments
Labels
component/gardenctl Gardener CLI kind/enhancement Enhancement, improvement, extension lifecycle/stale Nobody worked on this for 6 months (will further age) status/closed Issue is closed (either delivered or triaged)

Comments

@petersutter
Copy link
Member

What would you like to be added:
It should be possible to to get the path of the kubeconfig path of the current target, without parsing or evaluating the script returned by the kubectl-env command.

Why is this needed:
@petersutter petersutter added component/gardenctl Gardener CLI kind/enhancement Enhancement, improvement, extension labels Feb 22, 2022
@petersutter
Copy link
Member Author

maybe the kubeconfig path can be printed using the target view/describe command #120

@gardener-robot gardener-robot added the lifecycle/stale Nobody worked on this for 6 months (will further age) label Sep 6, 2022
@petersutter
Copy link
Member Author

This issue was mainly a requirement by @mandelsoft but got obsolete with the introduction of the kubeconfig command #152
/close

@gardener-robot gardener-robot added the status/closed Issue is closed (either delivered or triaged) label Oct 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
component/gardenctl Gardener CLI kind/enhancement Enhancement, improvement, extension lifecycle/stale Nobody worked on this for 6 months (will further age) status/closed Issue is closed (either delivered or triaged)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@petersutter @gardener-robot