I have created a private cluster and VM in the same network. I added VM's
internal IP in private cluster's master authorized network. From VM, after
obtaining cluster credentials, I am not able to execute kubectl commands.
However, if I add VM's external IP to master authorized network I am
is scenario -2 where I am trying to access private cluster
master from CICD project.
Any help is appreciated.
Thanks,
Vinita
On Wednesday, May 9, 2018 at 2:36:40 PM UTC-7, Mayur Nagekar wrote:
>
> What does `kubectl get endpoints kubernetes` show in your case ?
>
> -Mayur
>
> On Thu,
,
Vinita
On Friday, March 30, 2018 at 10:04:12 AM UTC-7, Tim Hockin wrote:
>
> Private cluster is private by default. You can not access the master from
> the internet. You can specifically change that with the master authorized
> networks feature, or you can access it from within your
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
Hi,
I am trying to use private cluster. I am able to create private cluster but
kubectl commands are not working. I am seeing connection time out error as
below -
kubectl run nginx --image=nginx --replicas=2error: failed to discover
supported resources: Get https://104.154.200.217/api: dial
