-
Notifications
You must be signed in to change notification settings - Fork 7
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
calico fails when creating pod #4
Comments
root@k8smaster:~# kubectl version
WARNING: This version information is deprecated and will be replaced with the output from kubectl version --short. Use --output=yaml|json to get the full version.
Client Version: version.Info{Major:"1", Minor:"26", GitVersion:"v1.26.0", GitCommit:"b46a3f887ca979b1a5d14fd39cb1af43e7e5d12d", GitTreeState:"clean", BuildDate:"2022-12-08T19:58:30Z", GoVersion:"go1.19.4", Compiler:"gc", Platform:"linux/amd64"}
Kustomize Version: v4.5.7
Server Version: version.Info{Major:"1", Minor:"26", GitVersion:"v1.26.0", GitCommit:"b46a3f887ca979b1a5d14fd39cb1af43e7e5d12d", GitTreeState:"clean", BuildDate:"2022-12-08T19:51:45Z", GoVersion:"go1.19.4", Compiler:"gc", Platform:"linux/amd64"}
root@k8smaster:~# calicoctl version
Client Version: v3.23.5
Git commit: 9e0398360
Cluster Version: v3.23.5
Cluster Type: k8s,bgp
root@k8smaster:~# etcdctl version
etcdctl version: 3.5.5
API version: 3.5 |
It works if I use flannel root@k8smaster:~# kubectl describe pod nginxpersistent
Pod 'nginxpersistent': error 'pods "nginxpersistent" not found', but found events.
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Pulling 12m kubelet Pulling image "nginx"
Normal Pulled 11m kubelet Successfully pulled image "nginx" in 15.459768881s (15.459859185s including waiting)
Normal Created 11m kubelet Created container nginxpersistent
Normal Started 11m kubelet Started container nginxpersistent |
I found a similar answer. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
No new pods are started
The text was updated successfully, but these errors were encountered: