Description
Operator Build: 2.2.1-125 (latest)
Couchbase Server: 6.6.2
Couchbase Cluster was created using test.yaml (attached) as provided in https://issues.couchbase.com/browse/K8S-2293
- 2 pods
- 1 pod running data only service.
- 1 pod running index only service.
Status:
Prateeks-MacBook-Pro:Downloads prateekkumar$ kubectl get pods
|
NAME READY STATUS RESTARTS AGE
|
cb-example-0000 1/1 Running 0 4m28s |
cb-example-0001 1/1 Running 0 4m15s |
couchbase-operator-57f874dc69-2v89t 1/1 Running 0 8m7s |
couchbase-operator-admission-6574f89486-2cpfc 1/1 Running 0 8m36s |
However when service status is checked, both the pods have 8092 port available on them.
Prateeks-MacBook-Pro:Downloads prateekkumar$ kubectl get svc
|
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S)
|
cb-example-0000 NodePort 10.80.5.174 <none> 8091:30320/TCP,18091:31313/TCP,11210:30917/TCP,11207:30099/TCP,8092:32150/TCP,18092:30241/TCP |
cb-example-0001 NodePort 10.80.8.96 <none> 8091:30167/TCP,18091:31088/TCP,11210:31814/TCP,11207:30753/TCP,8092:30381/TCP,18092:31726/TCP |
cb-example-srv ClusterIP None <none> 11210/TCP,11207/TCP |
cb-example-ui NodePort 10.80.9.188 <none> 8091:32125/TCP,18091:32380/TCP |
Is this expected ?
cbopinfo attached.
Attachments
Issue Links
- has to be done after
-
K8S-2293 Expose index/view NodePort service on data pods
-
- Closed
-