Re: [kubernetes-users] GKE Private cluster - accessing master

Hi Mayur, Now I have created new private cluster. I tried 2 scenarios - *Scenario - 1*. Executing kubectl commands from VM in same project within same network. I added VM's internal IP in master authorized network. I connected to cluster - gcloud container clusters get-credentials --zone

Re: [kubernetes-users] GKE Private cluster - accessing master

What does `kubectl get endpoints kubernetes` show in your case ? -Mayur On Thu, May 10, 2018 at 2:28 AM, Vinita wrote: > Hi Alan, > > Thanks for your reply. I tried your workaround but the certificate is not > valid for master's internal IP address. I get below error - >

Re: [kubernetes-users] GKE Private cluster - accessing master

Hi Alan, Thanks for your reply. I tried your workaround but the certificate is not valid for master's internal IP address. I get below error - Unable to connect to the server: x509: certificate is valid for 35.224.109.130, 10.118.16.1, 172.16.0.2, not 172.16.0.3Thanks, Vinita On Wednesday, May

Re: [kubernetes-users] GKE Private cluster - accessing master

Hi Vinita, I believe the problem is that currently "gcloud container clusters get-credentials" always writes the master's external IP address to ~/.kube/config. So kubectl always talks to that external IP address (via the external IP address of the VM it's running on). You should be able to