-
Notifications
You must be signed in to change notification settings - Fork 1
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
Merge with default KUBECONFIG if no other path is specified #37
Comments
Our action should also set the |
When we create cluster we can do not define |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Other Kubernetes configuration actions, including https://github.com/helm/kind-action and the
k3s
actions on the GHA marketplace, do write the resulting kubeconfig file to the default location.kube/config
. Our action should mimic this behavior by default if users do not specify thekubeconfig
input.I think our CLI does this by default now? Check with @zipofar. Maybe we can just drop the
--kubeconfig
argument fromuffizzi cluster create
?The goal is so workflows can follow our action with
kubectl
orhelm
without specifying--kubeconfig
, as seen in documentation for other Kubernetes configuration actions.The text was updated successfully, but these errors were encountered: