Re: [kubernetes-users] private cluster master access and ip

[Agrawal, Punit]

Incidentatlly, I just had a conversation with Manjot (PM) this morning.
It is not possible to get rid of the public IP for master since Google needs that to communicate to it for its management.

 

punit agrawal

dev-ops lead

new product development

ebay

 

 

From: <kubernet...@googlegroups.com> on behalf of Mauricio Castro <mauriciossan...@gmail.com>
Reply-To: "kubernet...@googlegroups.com" <kubernet...@googlegroups.com>
Date: Friday, September 7, 2018 at 9:50 AM
To: Kubernetes user discussion and Q&A <kubernet...@googlegroups.com>
Subject: [kubernetes-users] private cluster master access and ip

 

Hello all, I am starting with k8s in google, please help me with this doubt regarding private clusters.

 

I made it work  just fine based on a pre-defined subnet. great. all closed , all private, nodes have no public ip's, master range is 172.16.4.0/28 as expected and all is good.

I was assuming that with this I would only be able to access it (or at least this is what I wanted in the first place) the master with kubectl from inside the vpc against some master private ip from that range  172.16.4.0/28, but the only way I can get to my master with kubectl is by accessing its external public ip that ok I can restrict access to, but is there any other way to get to the master through a internal ip and get rid of the public ip altogether?

Thanks.

--
You received this message because you are subscribed to the Google Groups "Kubernetes user discussion and Q&A" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-use...@googlegroups.com.
To post to this group, send email to kubernet...@googlegroups.com.
Visit this group at https://groups.google.com/group/kubernetes-users.
For more options, visit https://groups.google.com/d/optout.