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
vagrant: Only set K8S_NODE_NAME if K8S=1 #11086
Conversation
Fixes: #11021 Signed-off-by: Jarno Rajahalme <jarno@covalent.io>
test-me-please |
This is not really tested in the CI, as if only affects the devVM started with |
Failed with weird error: restart-ginkgo |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks Jarno!
The |
Ginkgo provisioning fail. |
As said, this is ready to merge without passing the CI. |
The PR that introduced the bug was backported to v1.7 and v1.6, thus breaking the runtime1 VM there. The fix is really small and doesn't conflict, so I think it's worth backporting to v1.7 to ease backport tests (I usually spin up the runtime1 VM to have the appropriate Go version when I test-compile backport PRs). I'm adding the needs-backport/1.7 label and I will add this commit to #13402. |
This allows Cilium to start without K8s in the Dev VM started with './contrib/vagrant/start.sh'.
Fixes: #11021
Signed-off-by: Jarno Rajahalme jarno@covalent.io