Re: [kubernetes-users] How to keep full Kubernetes private?

On Monday, 22 January 2018 19:42:16 UTC, Tim Hockin wrote: > VPN is the normal answer - you are extending your private space into the > cloud. > > On Sun, Jan 21, 2018 at 8:39 AM, Lorenz Vanthillo > wrote: > > Thanks for your reply. Now I want to use GKE to create

Re: [kubernetes-users] How to keep full Kubernetes private?

VPN is the normal answer - you are extending your private space into the cloud. On Sun, Jan 21, 2018 at 8:39 AM, Lorenz Vanthillo wrote: > Thanks for your reply. Now I want to use GKE to create my Kubernetes > cluster, so my master IP will be public. I read something

Re: [kubernetes-users] How to keep full Kubernetes private?

Thanks for your reply. Now I want to use GKE to create my Kubernetes cluster, so my master IP will be public. I read something here ( https://cloud.google.com/kubernetes-engine/docs/how-to/authorized-networks) about how we can secure this. For our cluster we *disabled the GKE Ingress Controller*,

Re: [kubernetes-users] How to keep full Kubernetes private?

Important - this is for kubernetes on GCE, not for GKE. GKE masters use public IP, even though the traffic never leaves Google. We are looking at how best o support true private GKE. On Jan 20, 2018 2:34 PM, "Tim Hockin" wrote: > You should not need a public IP unless you

Re: [kubernetes-users] How to keep full Kubernetes private?

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" wrote: > We want to start using Kubernetes on Google Cloud

[kubernetes-users] How to keep full Kubernetes private?

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