Clara Deployment - Error: OWNER%!D(MISSING)TILLER: dial tcp 10.96.0.1:443: i/o timeout

[deva1]

After SDK indtalaltion , helm ls is giving an error
2020-12-02 05:29:11 [INFO]: Clara Deploy SDK Prerequisites installed successfully!
:~/bootstrap# helm ls
Error: Get https://10.96.0.1:443/api/v1/namespaces/kube-system/configmaps?labelSelector=OWNER%!D(MISSING)TILLER: dial tcp 10.96.0.1:443: i/o timeout

OS- Ubuntu 18
Clara bootstrap - with helm 2.15

Can we fix this issue?
-D

[kkersten]

Hi Deva1,

Thanks for your interest in Clara Deploy.

Can you share the output of the bootstrap script? I would like to confirm that all steps completed successfully.

Will you also share the output of kubectl get pods -A?

Thanks,
Kris

[deva1]

Hi Kris,

Thanks a lot for your response.

PFA boot file o/p .

Look forward.

-Deva

bootstrap-install.txt (27.4 KB)

[kkersten]

Hi Deva,

The kubectl get pods -A output shows one of the coredns pods with an error state. The coredns pods should be redundant for HA, but this indicates some problem with networking. Was there a previous k8s cluster on this machine? If so, there may be some stale iptables rules that are interfering. You can flush them as described in this post:

Clara platform start - connect: no route to host

Hi Darren, Kubernetes may leave some residual iptables rules that can cause routing issues on a reinstall. Check the state of the currently running system pods with: kubectl get pods -n kube-system You may see the coredns pods in CrashLoopBackOff. If you didn’t explicitly flush iptables during the reinstall, try the following: sudo systemctl stop kubelet sudo systemctl stop docker sudo iptables --flush sudo iptables -t nat --flush sudo systemctl start kubelet sudo systemctl start dock…

If not, we need to look into the current cluster state. Will you provide the output of the following:
kubectl describe pod <failing coredns pod name>
kubectl logs <failing coredns pod name>
kubectl get ep -A
kubectl get svc -A

Thanks,
Kris