liveBook · Manning

Managed certificate

As explained in Kubernetes for Developers

A managed certificate is a cloud-managed certificate resource whose provisioning, renewal, and deployment are handled automatically for specified domains.

A managed certificate lets GKE provision and manage TLS certificates for specified domains automatically. You prove domain ownership, create a GKE-specific ManagedCertificate object listing the domains, and reference it from an Ingress. section 7.2.1

Using a managed certificate replaces several manual certificate tasks:

  • Skip the certificate-authority signing step. section 7.2.1
  • Avoid copying a private key and certificate into Kubernetes as a Secret. section 7.2.1
  • Reference the managed certificate from the Ingress so HTTPS traffic can use the provisioned certificate. section 7.2.1

Publishing example.com

After proving ownership of example.com in Google Cloud, create a ManagedCertificate object for the domain and connect it to the GKE Ingress. Google then provisions and manages the certificate automatically. section 7.2.1

How Kubernetes for Developers covers it

How deep it goes
Explains ownership verification, domain listing, and Ingress reference, but defers implementation details to official documentation.
Examples
Uses domain ownership for example.com and contrasts managed certificates with manually created TLS Secrets.
What it assumes
Assumes GKE, Ingress, domains, and TLS basics while explaining the managed-certificate workflow directly.
What you can do after
Configure a GKE Ingress to use an automatically provisioned certificate for specified domains.
How it connects
Connects managed certificates with GKE, Kubernetes Ingress, TLS, certificate authorities, and Kubernetes Secrets.

This explainer was generated by Manning's knowledge graph from the text of Kubernetes for Developers. The section links point to the parts of the book it draws on.