/
Ensure Kubernetes Cluster is created with Private cluster enabled

Ensure Kubernetes Cluster is created with Private cluster enabled

Description: 

A private cluster is a cluster that makes your master inaccessible from the public internet. In a private cluster, nodes do not have public IP addresses, so your workloads run in an environment that is isolated from the internet. Nodes have addressed only in the private RFC 1918 address space. Nodes and masters communicate with each other privately using VPC peering.



Solution: 

It is recommended that all Columbia GCP traffic remain in the bounds of the Columbia intranet. For this reason, private clusters are a must with inbound traffic only being accessible to CU IP ranges.



Reference: 

https://cloud.google.com/kubernetes-engine/docs/how-to/private-clusters

Related content

Ensure Master authorized networks is set to Enabled on Kubernetes Engine Clusters
Ensure Master authorized networks is set to Enabled on Kubernetes Engine Clusters
More like this
Ensure Kubernetes Cluster is created with Alias IP ranges enabled
Ensure Kubernetes Cluster is created with Alias IP ranges enabled
More like this
Ensure Network policy is enabled on Kubernetes Engine Clusters
Ensure Network policy is enabled on Kubernetes Engine Clusters
More like this
Ensure Pod Security Policy controller is enabled on the Kubernetes Engine Clusters
Ensure Pod Security Policy controller is enabled on the Kubernetes Engine Clusters
More like this
Ensure Kubernetes Clusters are configured with Labels
Ensure Kubernetes Clusters are configured with Labels
More like this
Ensure Kubernetes Cluster is created with Client Certificate enabled
Ensure Kubernetes Cluster is created with Client Certificate enabled
More like this