Description
I am trying to install couchbase cluster on kubernetes deployment (Centos), created using vagrant environment nodes.
[root@k8s-master couchbase-operator]# cat /etc/*release* |
CentOS Linux release 7.0.1406 (Core) |
NAME="CentOS Linux" |
The status of all the master/worker nodes seem fine:
[root@k8s-master couchbase-operator]# kubectl get nodes |
NAME STATUS ROLES AGE VERSION
|
k8s-master Ready master 1d v1.9.1 |
worker-node-1 Ready <none> 59m v1.9.1 |
worker-node-2 Ready <none> 1d v1.9.1 |
worker-node-3 Ready <none> 1h v1.9.1 |
The status of the couchbase-operator deployment seems fine :
|
|
[root@k8s-master couchbase-operator]# kubectl get deployments |
NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE
|
couchbase-operator 1 1 1 0 11m |
The couchbase-operator pod is also in running state:
|
|
[root@k8s-master couchbase-operator]# kubectl get pods |
NAME READY STATUS RESTARTS AGE
|
couchbase-operator-5687d4888-scqwx 0/1 Running 0 12m |
However when i do describe pod, I am seeing that the readiness check is failing:
Events:
|
Type Reason Age From Message
|
---- ------ ---- ---- -------
|
Normal Scheduled 12m default-scheduler Successfully assigned couchbase-operator-5687d4888-scqwx to worker-node-1 |
Normal SuccessfulMountVolume 12m kubelet, worker-node-1 MountVolume.SetUp succeeded for volume "default-token-82jzx" |
Normal Pulled 12m kubelet, worker-node-1 Container image "couchbase/couchbase-operator:v1" already present on machine |
Normal Created 12m kubelet, worker-node-1 Created container |
Normal Started 12m kubelet, worker-node-1 Started container |
Warning Unhealthy 2m (x200 over 12m) kubelet, worker-node-1 Readiness probe failed: HTTP probe failed with statuscode: 500 |
After executing the command: example/rbac/create_role.sh, the couchbase cluster is created successfully:
[root@k8s-master couchbase-operator]# kubectl create -f example/couchbase-cluster.yaml |
couchbasecluster "cb-example" created |
Not sure what implications the failed Readiness probe has. Please let me know if you need more information.
Attachments
Issue Links
- duplicates
-
K8S-105 Setup a Kubernetes cluster on vagrants and test the operator
-
- Closed
-