29/10/2026
𝗘𝘅𝗰𝗹𝘂𝘀𝗶𝘃𝗲 𝗢𝗽𝗲𝗻𝗦𝗵𝗶𝗳𝘁 𝗖𝗼𝗻𝗰𝗲𝗽𝘁 𝟭𝟬 - "TLS & certificates in OpenShift"
Imagine running multiple nodes in a Telco cluster and tracking security certificate expiry for each one. The overhead of manually generating a security certificate and the private key in each cycle, and manually binding a TLS secret with each ingress resource to decrypt what is coming from outside the cluster.
All of this is automated with the built-in 𝗧𝗟𝗦 𝗿𝗼𝘂𝘁𝗶𝗻𝗴 𝗲𝗻𝗴𝗶𝗻𝗲, specifically the native Route API and the built-in 𝗦𝗲𝗿𝘃𝗶𝗰𝗲 𝗖𝗔 𝗢𝗽𝗲𝗿𝗮𝘁𝗼𝗿 in OpenShift.
1. The Internal Service CA Operator (Zero-Touch PKI). OpenShift automatically:
- Generates a valid internal X.509 certificate and private key.
- Mounts it into the target application pod.
- Continuously rotates the certificate before it expires- with zero external plugins.
2. In OpenShift, the "Route" resource natively defines three distinct TLS architectures directly in its specification:
- Edge: Decrypts at the cluster perimeter router.
- Passthrough: Encrypted traffic bypasses the router entirely and goes untouched straight to the pod.
- Re-encryption (Exclusive Pattern): Decrypts incoming traffic with an external public certificate at the edge, inspects it, and immediately re-encrypts it using an internal certificate before sending it across the internal network to the pod.
Standard Kubernetes Ingress has no native concept of re-encryption.
Using OpenShift, you are not dependent on external components (like NGINX), install a 3rd-party badge-making vendor (cert-manager), and manually program how TLS-bounded secrets inspect packets before they reach the destination