This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
Gari Singh is a Product Manager at Google Cloud focused on Google Kubernetes Engine (GKE). He spends a majority of his time promoting containers, Kubernetes and GKE and works with multiple GKE customers across all industries.
Using
https://cloud.google.com/build/docs/private-pools/accessing-private-gke-clusters-with-cloud-build-private-pools
with a couple modifications, I'm able to use this pattern to access the
new PSC-based private clusters (created with 1.29.3 and late...
GKE does not currently support enabling swap memory for nodes / pods. We
are tracking the feature in OSS and will add options for configuring
this once it and other related features become generally stable and
available.
You should definitely use a private cluster in production if you can.
Unless you need your nodes to have public IP addresses, private clusters
are the way to go. And actually, with the current private cluster
architecture, as long as you use GKE vers...
There is not global setting for this, but you can use GCPBackendPolicy
to attach IAP policy as part of deploying services. apiVersion:
networking.gke.io/v1 kind: GCPBackendPolicy metadata: name:
backend-policy spec: default: iap: enabled: true oauth2...