Stargate pod cannot resolve k8ssandra-seeder when kubernetes cluster domain name is different

82 views
Skip to first unread message

Eren Cankurtaran

unread,
Mar 24, 2021, 2:10:08 PM3/24/21
to K8ssandra Users
Hi,
I've deployed kubernetes cluster with kubespray and the cluster domain name is 

the problem is k8ssandra-dc1-stargate is stuck at Init mode 

```
➜  ~ kgp
NAME                                                READY   STATUS      RESTARTS   AGE
dnstools                                            1/1     Running     0          41s
k8ssandra-cass-operator-7d5df6d49-qp4d9             1/1     Running     0          3h42m
k8ssandra-dc1-default-sts-0                         2/2     Running     0          3h42m
k8ssandra-dc1-stargate-5c488fc695-lcx9w             0/1     Init:0/1    0          3h42m
k8ssandra-grafana-679b4bbd74-c7772                  2/2     Running     0          3h42m
k8ssandra-kube-prometheus-operator-85695ffb-cst56   1/1     Running     0          3h42m
k8ssandra-reaper-655fc7dfc6-nrcjz                   1/1     Running     1          3h40m
k8ssandra-reaper-operator-79fd5b4655-fx4vc          1/1     Running     0          3h42m
k8ssandra-reaper-schema-6sz88                       0/1     Completed   0          3h40m
nfs-subdir-external-provisioner-6b5bbcb66b-46mkz    1/1     Running     0          9h
prometheus-k8ssandra-kube-prometheus-prometheus-0   2/2     Running     1          3h42m
```
I've looked at stargate pod with docker logs  and i get 

```
docker logs k8s_wait-for-cassandra_k8ssandra-dc1-stargate-5c488fc695-lcx9w_default_2202d8ad-0e38-4138-9906-f902ad66a6a9_0

and the output is 
** server can't find k8ssandra-seed-service.default.svc.cluster.local: NXDOMAIN

Server: 169.254.25.10

``` 

with nslookup i've tried  and it can resolve service successfully
Server: 169.254.25.10
Address: 169.254.25.10#53

Address: 10.233.88.5
```

i think in stargate pod script does not dynamically change cluster domain name 

How can i resolve the problem? 

Best regards,
Eren Cankurtaran

Michael Burman

unread,
Mar 24, 2021, 2:49:54 PM3/24/21
to K8ssandra Users
Hi,

You could setup top-level value clusterDomain: "b-k8s.beartell.org" to your helm deployment values. So at the end of helm install, --set clusterDomain=b-k8s.beartell.org

  -  Micke

Reply all
Reply to author
Forward
0 new messages