You should not need a public IP unless you access public things. Stuff like GCR (inside Google) will be ok. If you need to egress, you need a NAT (diy for now).
On Jan 20, 2018 10:29 AM, "lvthillo" <lorenz.vanthi...@gmail.com> wrote: > We want to start using Kubernetes on Google Cloud Platform. We want that > this Kubernetes (and all services, etc) are only accessible from inside our > network. It's for development purposes so we don't need public access. (But > we want internet access from inside our cluster, for example to download > dependencies in our Jenkins pod). > > We have some VPN service for users who are working remotely to connect to > our network. > Here I was reading about another solution to make the Kubernetes cluster > private: https://engineering.bitnami.com/articles/creating-private- > kubernetes-clusters-on-gke.html > > I'm searching for ideas/replies/opinions of people who have this > experience with it. > > -- > 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-users+unsubscr...@googlegroups.com. > To post to this group, send email to kubernetes-users@googlegroups.com. > Visit this group at https://groups.google.com/group/kubernetes-users. > For more options, visit https://groups.google.com/d/optout. > -- 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-users+unsubscr...@googlegroups.com. To post to this group, send email to kubernetes-users@googlegroups.com. Visit this group at https://groups.google.com/group/kubernetes-users. For more options, visit https://groups.google.com/d/optout.
