Open liweis opened 1 month ago
@liweis I think what you want to check out are the logs for the tigera operator pod, do kubectl get pods -n tigera-operator
to get the pod name, then kubectl logs -n tigera-operator tigera-operator-XXXXX
(with the actual pod name you got from the previous command). Could you post the results here, along with the output of kubectl get tigerastatus
and maybe also kubectl describe tigerastatus
?
@liweis I think what you want to check out are the logs for the tigera operator pod, do
kubectl get pods -n tigera-operator
to get the pod name, thenkubectl logs -n tigera-operator tigera-operator-XXXXX
(with the actual pod name you got from the previous command). Could you post the results here, along with the output ofkubectl get tigerastatus
and maybe alsokubectl describe tigerastatus
?
@coutinhop Thanks for your reply.
kubectl logs -n tigera-operator tigera-operator-XXXXX
gets:
And also:
btw, the kubeadm init cmd I use is:
sudo kubeadm init --cri-socket unix:///var/run/cri-dockerd.sock --apiserver-advertise-address=[host ip address] --pod-network-cidr=192.168.0.0/16
--apiserver-advertise-address=[host ip address]
could you elaborate? the tigera operator is failing to reach the kubernetes apiserver on 10.96.0.1 from the logs you posted, should it be looking for the apiserver in a different address?
could you also post the output of kubectl get svc -A -o wide
?
--apiserver-advertise-address=[host ip address]
could you elaborate? the tigera operator is failing to reach the kubernetes apiserver on 10.96.0.1 from the logs you posted, should it be looking for the apiserver in a different address?
could you also post the output of
kubectl get svc -A -o wide
?
@coutinhop
--apiserver-advertise-address=[host ip address]
could you elaborate? the tigera operator is failing to reach the kubernetes apiserver on 10.96.0.1 from the logs you posted, should it be looking for the apiserver in a different address?
could you also post the output of
kubectl get svc -A -o wide
? should I change the calico setup configs to use the api server ip showed here ?
Expected Behavior
pods are running in calico-system namespace after a fresh installation
Current Behavior
no pods in calico-system namespace, and
kubectl logs installation.operator.tigera.io/default
gets:error: no kind "Installation" is registered for version "operator.tigera.io/v1" in scheme "pkg/scheme/scheme.go:28"
Possible Solution
Steps to Reproduce (for bugs)
Context
Your Environment