We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
A user may want to provide a custom kubeconfig path as opposed to strictly targeting: ~/.kube/config
kubeconfig
~/.kube/config
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)
eksup analyze [OPTIONS] --cluster <CLUSTER>
--kubeconfig ~/.kube/config
Additionally, the user could set the KUBECONFIG environment variable, resulting in the equivalent of --kubeconfig:
KUBECONFIG
--kubeconfig
KUBECONFIG=/tmp/123abc-generated-config eksup analyze [OPTIONS] --cluster <CLUSTER>
No response
The text was updated successfully, but these errors were encountered:
No branches or pull requests
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
The text was updated successfully, but these errors were encountered: