-
Notifications
You must be signed in to change notification settings - Fork 378
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
deploy craned didn't READY #763
Comments
Can't see any error logs, pls provide more info. |
my local kubernetes cluster based on centos 7.9,the kubernetes version is v1.27.1, hem version is v3.11.3, kind version is 0.18.0, |
[root@k8s-master01 crane-lab]# kubectl describe deploy/craned -n crane-system Available False MinimumReplicasUnavailable Normal ScalingReplicaSet 5m1s deployment-controller Scaled up replica set craned-75d5fcff49 to 1 |
Your k8s version is too high, you can use kindest/node:v1.21.1 to install a lower k8s cluster |
I used the kindest/node:v1.21.1 , just I install the kubectl version is : v1.27.1 [root@crane-master ~]# docker ps -a Available False MinimumReplicasUnavailable Normal ScalingReplicaSet 4m57s deployment-controller Scaled up replica set craned-75d5fcff49 to 1 Warning FailedScheduling 5m7s (x3 over 5m23s) default-scheduler 0/1 nodes are available: 1 node(s) had taint {node.kubernetes.io/not-ready: }, that the pod didn't tolerate. |
the problem is server dns,,you should set he DNS 8.8.8.8,and try installation |
Describe the bug
deploy craned didn't ready
Reproduce steps
follow the install steps,and Verify Installation ,get the status
Expected behavior
like the installation guide,the deploy craned should be Ready and available
Screenshots
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: