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

Feature request: Capability to pass custom kubeconfig path #41

Open
mbeacom opened this issue Apr 1, 2023 · 0 comments
Open

Feature request: Capability to pass custom kubeconfig path #41

mbeacom opened this issue Apr 1, 2023 · 0 comments
Labels
feature-request Request for a new feature

Comments

@mbeacom
Copy link

mbeacom commented Apr 1, 2023

Use case

A user may want to provide a custom kubeconfig path as opposed to strictly targeting: ~/.kube/config

Solution/User Experience

This could subsequently be used by any end user:

eksup analyze [OPTIONS] --cluster <CLUSTER> --kubeconfig /tmp/123abc-generated-config

The default workflow of:

eksup analyze [OPTIONS] --cluster <CLUSTER> would result in automatic use of: --kubeconfig ~/.kube/config (or rather, default to ~/.kube/config)

Additionally, the user could set the KUBECONFIG environment variable, resulting in the equivalent of --kubeconfig:

KUBECONFIG=/tmp/123abc-generated-config eksup analyze [OPTIONS] --cluster <CLUSTER>

Alternative solutions

No response

@mbeacom mbeacom added feature-request Request for a new feature triage labels Apr 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request Request for a new feature
Projects
Status: Todo
Development

No branches or pull requests

2 participants