-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
GKE Pod Failed to create cluster with "failed to init node with kubeadm" #997
Comments
please see: #303 |
this will not work, you're nodes will be out on the host in a different namespace. you'll have to follow the details in #303 to get this working. additionally, while we do run kind on GKE for kubernetes CI because that is where Kubernetes's CI runs, we do not recommend it over VM based CI. an additional layer of "Containers 'in' Containers" is a bit of a footgun. |
specifically, details are in #303 (comment) unfortunately this "mount the docker socket" pattern is unlikely to ever work well for kind, due to the nature of how containers work, so this is not supported... EDIT: dind however is supported, if tricky and non-ideal (see the link). |
Thank you very much @BenTheElder - this definitely felt like quite a big hack, running in kubernetes pods sounds much more sensible. Perfect. I will have a look at #303 and will try that approach instead! |
I appreciate your understanding. #303 is not great either, but done carefully can help prevent resource leakage and avoids some of the network namespace issues. We use https://github.com/kubernetes/test-infra/tree/master/images/krte in Kubernetes CI, formerly (and for a few things still) https://github.com/kubernetes/test-infra/tree/master/images/kubekins-e2e these are at |
What happened:
We are trying to run our end to end tests in a GKE kubernetes cluster, creating the cluster from within the pod and then running all the tests. This has been unsuccessful so far due to the error (as shown below). I provide the pod spec used, together with the output of the command (with the error), and the version of the K8s cluster and docker server.
I also tried to find different issues such as #982 (got fixed updating), #928 (doesn't seem same problem).
The issue fails with and without config file, which is as follows:
This is the configuration used in the pod in order to run (tried multiple different combinations):
This is the output of the command
kind create cluster --loglevel debug
:This is the version of the kubernetes cluster:
This is the version of my docker server (through
docker info
command within the pod):The text was updated successfully, but these errors were encountered: