Open jichenjc opened 8 months ago
@sthaha any insight on this or suggestions? Thanks
@jichenjc Are you using docker or podman? From the logs it looks similar to this issue: https://github.com/kubernetes-sigs/kind/issues/3412
I am using docker.. is it need to be podman ?
No, the issue is with podman. With docker it should work🤔
@jichenjc, does make cluster-up work for you from the kepler
repo?
um.. seems not , I got exactly same issue , so definitely something need to be updated
I always use kind create one k8s node before but with operator I have to follow the make cluster-up
way..
so first time see this problem
kind create
should work for operator as well but a lot of things that the cluster-up
does will have to manually done.
I am stucking at 2nd kind creation (because the kind is not able to join the first kind ) due to DNS setup
kind-control-plane
is not able to be resolved in the worker node's DNS , it might need some update ..
I1201 03:22:51.209370 174 round_trippers.go:553] GET https://kind-control-plane:6443/api/v1/namespaces/kube-public/configmaps/cluster-info?timeout=10s in 2 milliseconds
I1201 03:22:51.209458 174 token.go:217] [discovery] Failed to request cluster-info, will try again: Get "https://kind-control-plane:6443/api/v1/namespaces/kube-public/configmaps/cluster-info?timeout=10s": dial tcp: lookup kind-control-plane on 9.20.136.11:53: no such host
um.. seems not , I got exactly same issue , so definitely something need to be updated I always use kind create one k8s node before but with operator I have to follow the make cluster-up way.. so first time see this problem
update on this , I used wrong folder, in kepler
folder if you run make cluster-up
only one kind pod create and it is ok to run kepler functions there ..
looks like this is different to https://github.com/sustainable-computing-io/kepler-operator/issues/260 I believe it's due to DNS settings and the worker node is not able to resolve kind-control-plane can someone help proivde some suggestions?