https://bravenewgeek.com/tag/gclb/Recent content in Gclb on Brave New GeekHugoen-usWed, 24 Jun 2020 11:31:44 -0500https://bravenewgeek.com/using-google-managed-certificates-and-identity-aware-proxy-with-gke/Wed, 24 Jun 2020 11:31:44 -0500https://bravenewgeek.com/using-google-managed-certificates-and-identity-aware-proxy-with-gke/<p>Ingress on Google Kubernetes Engine (GKE) uses a Google Cloud Load Balancer (GCLB). GCLB provides a single anycast IP that fronts all of your backend compute instances along with a lot of other <a href="https://cloud.google.com/load-balancing">rich features</a>. In order to create a GCLB that uses HTTPS, an SSL certificate needs to be associated with the ingress resource. This certificate can either be <a href="https://cloud.google.com/load-balancing/docs/ssl-certificates/self-managed-certs">self-managed</a> or <a href="https://cloud.google.com/load-balancing/docs/ssl-certificates/google-managed-certs">Google-managed</a>. The benefit of using a Google-managed certificate is that they are provisioned, renewed, and managed for your domain names by Google. These managed certificates can also be configured directly with GKE, meaning we can configure our certificates the same way we declaratively configure our other Kubernetes resources such as deployments, services, and ingresses.</p>