liveBook · Manning

Self-signed certificate

As explained in Kubernetes for Developers

A self-signed certificate is a certificate signed by its own subject rather than by a trusted certificate authority.

A self-signed certificate is signed by its own subject instead of a trusted certificate authority. It encrypts the connection, but does not verify the server’s identity, so browsers display warnings. section 7.2.1

Development HTTPS endpoint

Create a certificate for example.com, configure it as my-tls-cert, apply the Ingress, and map example.com to the Ingress IP. The browser may warn because the certificate is untrusted.

How Kubernetes for Developers covers it

How deep it goes
Explains certificate creation, Kubernetes Secret storage, Ingress configuration, DNS mapping, and browser warnings.
Examples
Uses OpenSSL commands, a my-tls-cert Secret, an example.com Ingress, and a local hosts-file mapping.
What it assumes
Assumes basic Kubernetes networking context while teaching certificate files, TLS Secrets, and Ingress references.
What you can do after
Apply it via OpenSSL, kubectl, and an Ingress configuration to expose an encrypted endpoint.
How it connects
Connects TLS with certificate authorities, Kubernetes Secrets, Ingress, HTTPS, and DNS.

Also explained in

Compare how 4 books explain self-signed certificate →

Related concepts

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.