configuration of voyager connect kubernetes is unreasonable

[like-inspur]

Despite create voyager in way of deployment, voyager connect kubernetes still needs --kubeconfig or --master. When I create kubernetes cluster in way of kubespary, I config --kubeconfig is /etc/kubernetes/node-kubeconfig.yaml like this, the error is unauthorized apiVersion: v1 kind: Config clusters:

• name: local cluster: certificate-authority: /etc/kubernetes/ssl/ca.pem server: https://127.0.0.1:6443 users:
• name: kubelet user: client-certificate: /etc/kubernetes/ssl/node-node1.pem client-key: /etc/kubernetes/ssl/node-node1-key.pem contexts:
• context: cluster: local user: kubelet name: kubelet-cluster68 current-context: kubelet-cluster68

When I config --master is http://10.110.17.68:8080, it succeed. But it can't support multi master url, how can I use voyager in HA environment in a simple way? Thank you!

[tamalsaha]

Hi, Sorry for slow response. Voyager operator by default connects to Kubernetes master using incluster config, which uses kubernetes service to connect to api server. Do you now have a kubernetes Service in your default namespace?

[like-inspur]

I config master with https://kubernetes.default.svc:443, but pod run error like this: @tamalsaha F0107 12:05:06.350179 1 run.go:126] Get https://kubernetes.default.svc:443/apis/apiextensions.k8s.io/v1beta1/customresourcedefinitions/ingresses.voyager.appscode.com: x509: certificate signed by unknown authority