GKE relies on public IPs to access the hosted master, for now. On Tue, Jul 18, 2017 at 1:46 AM, nnilesh7...@gmail.com <cybage.almdev...@gmail.com> wrote: > I'm trying to launch Google Container Engine (GKE) in Private GCP network > Subnet. > > I have created custom Google Cloud VPC, then I have created custom Private > Network Access Subnet too under that VPC. > > 1) When I create GKE cluster with Private Subnet, still my Kubernetes nodes > assigned with Public IP. Why it is so ? As per Google Document private > instance should get Private IP. > > 2) If I create cluster in Private, can I connect my container application to > Google SQL instance ? > > 3) Is any recommendation to launch GKE cluster should launched in Public > Subnet only, not in Private Subnet ? > > -- > 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.
