Skip to content
This repository has been archived by the owner on Mar 10, 2021. It is now read-only.

Used master-1 IP instead of loadbalancer IP for HA cluster #41

Open
themsay opened this issue Aug 12, 2019 · 0 comments
Open

Used master-1 IP instead of loadbalancer IP for HA cluster #41

themsay opened this issue Aug 12, 2019 · 0 comments

Comments

@themsay
Copy link

themsay commented Aug 12, 2019

Hi, looking at scripts/generate-kubeconfig-kube-proxy content

kubectl config set-cluster kubernetes-the-hard-way
[...]
--server=https://192.168.199.10:6443   # master-1 IP address
[...]

It should be loadbalancer IP address 192.168.199.40:6443 for HA, which eliminate single point of failure.

I changed to --server=https://192.168.199.40:6443 and got this on test:

$> kubectl exec -ti $POD_NAME -- nslookup kubernetes
Server:    10.32.0.10
Address 1: 10.32.0.10

nslookup: can't resolve 'kubernetes'
command terminated with exit code 1
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant