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

chore(conf) update Kind version up to v0.7.0 #625

Merged
merged 4 commits into from
Mar 17, 2020

Conversation

lobkovilya
Copy link
Contributor

Summary

I was following the steps of developers guide and faced issues with Kind v0.5.1.
The command kind load ... returned exit code 126 and nothing more.

@lobkovilya lobkovilya requested a review from a team March 12, 2020 13:11
Makefile Outdated Show resolved Hide resolved
@lobkovilya
Copy link
Contributor Author

In the new version Kind deleted command kind get kubeconfig-path. Instead that command now there are two alternatives:

  • kubectl config use-context kind-kuma
  • kind get kubeconfig --name kuma > kube-confg

The first one is not really convenient since it changes the global state of environment.
The second one is more preferable but it requires to manage path to kubeconfig manually. I made implementation that saves KUBECONFIG file to build/kubeconfig. I understand that build is not really suitable place for such kind of config. So I believe we should consider the right place for it.

  • ~/.kube/kind-kuma-config
  • config/kuma-config and etc.

@jakubdyszkiewicz what do you think about it?

@lobkovilya lobkovilya merged commit 81b2616 into kumahq:master Mar 17, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants