-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Kind v0.6.0 deprecates kind get kubeconfig-path
#1796
Comments
/kind documentation |
We'll also need to backport the quick start changes to the release-0.2 branch |
I hit this problem today. Thanks for opening the issue @b2jrock. |
Looks like clusterctl has an issue with this as well. See #1801. I have a backport ready, but I don't want to recommend kind v0.6.0 if it's non-functional with that version. |
We should update all docs to be based on kind 0.6+ |
/help |
@joonas: Please ensure the request meets the requirements listed here. If this request no longer meets these requirements, the label can be removed In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/assign |
Per kubernetes-sigs/cluster-api#1796, the `kind get kubeconfig-path` command no longer works. Update makefile to create kube-bench local kubeconfig and use that.
Per kubernetes-sigs/cluster-api#1796, the `kind get kubeconfig-path` command no longer works. Update makefile to create kube-bench local kubeconfig and use that.
Per kubernetes-sigs/cluster-api#1796, the `kind get kubeconfig-path` command no longer works. Update makefile to create kube-bench local kubeconfig and use that.
Per kubernetes-sigs/cluster-api#1796, the `kind get kubeconfig-path` command no longer works. Update makefile to create kube-bench local kubeconfig and use that.
Well, how can i get the path of kubeconfig when kind is upgraded to v0.9.0? Anyone can help? |
@Thor-wl I'm not sure you can still get the path, but you can export a kubeconfig via Afaik it also adds the credentials/config to your current kubeconfig (you just have to use the right context then). |
What steps did you take and what happened:
[A clear and concise description on how to REPRODUCE the bug.]
When following the installation guide in the book, when setting
KUBECONFIG
environment variable using the command listed, kind throws a deprecation warning.What did you expect to happen:
No deprecation warning from kind.
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
I think the context command it suggests is also needed.
Environment:
kubectl version
): 1.16.3/etc/os-release
): N/A/kind bug
The text was updated successfully, but these errors were encountered: