Open mauilion opened 3 years ago
When deploying cilium using cilium-cli for the first time. I brought up a cluster without kube-proxy.
When running cilium install --kube-proxy-replacement strict the install fails as pods are unable to connect to the k8s apiserver.
--kube-proxy-replacement strict
In the logs of the pods I can see that it's trying to connect to the internal service ip for the apiserver.
the helm install manages this by allowing the installer to set k8sServiceHost and k8sServicePort.
k8sServiceHost
k8sServicePort
For cilium-cli since we are assuming the creds of the configured kubectl we could populate those values from:
kubectl config view --minify -o jsonpath={.clusters[].cluster.server} https://10.80.0.10:6443
--minify ensures that we are looking only at values from the current kubeconfig context.
--minify
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
When deploying cilium using cilium-cli for the first time. I brought up a cluster without kube-proxy.
When running cilium install
--kube-proxy-replacement strict
the install fails as pods are unable to connect to the k8s apiserver.In the logs of the pods I can see that it's trying to connect to the internal service ip for the apiserver.
the helm install manages this by allowing the installer to set
k8sServiceHost
andk8sServicePort
.For cilium-cli since we are assuming the creds of the configured kubectl we could populate those values from:
--minify
ensures that we are looking only at values from the current kubeconfig context.