Openshift Reencrypt Route

Published
Length
3 min read

Luis Felipe Dias

All posts

An openshift reencrypt route terminates public TLS traffic at the router and opens a new TLS session to the pod. This setup keeps network traffic encrypted both outside and inside the cluster. Platform teams often use this route type for apps that handle private data. Still, broad cluster roles often give engineers full access to route keys and pod shells. How an openshift reencrypt route works A standard edge route ends encryption at the ingress router and sends plain traffic to the pod. A p

Your coding agents run with your access.

Claude Code reaches prod with a developer's credentials, and approval prompts get clicked through. hoop.dev checks every query, masks sensitive data, and holds risky changes for a human.

An openshift reencrypt route terminates public TLS traffic at the router and opens a new TLS session to the pod. This setup keeps network traffic encrypted both outside and inside the cluster. Platform teams often use this route type for apps that handle private data. Still, broad cluster roles often give engineers full access to route keys and pod shells.

How an openshift reencrypt route works

A standard edge route ends encryption at the ingress router and sends plain traffic to the pod. A passthrough route sends encrypted traffic straight to the pod without checking it at the router. The reencrypt option sits between those two models. The ingress router holds a public TLS key and certificate for outside clients. When a user sends a request, the router checks and decrypts that outside traffic first.

Next, the router starts a fresh TLS session with the destination service inside the cluster. To do this safely, the route needs a destination CA certificate. The router uses this CA certificate to trust the internal certificate that the pod presents. In many clusters, a built-in service CA controller makes and rotates these internal pod certificates. This design ensures that no plain text traffic travels across the internal pod network.

How role rules control route and pod access

Setting up network encryption is only half of the security puzzle for cluster admins. You also need to control who can edit route rules or read certificate secrets. In the underlying Kubernetes RBAC system, a Role sets permissions within a single namespace. A ClusterRole sets permissions across the whole cluster. Both role types hold rules that are purely additive, which means there are no deny rules.

A RoleBinding links a user or group to a Role inside one namespace. A ClusterRoleBinding grants those permissions across every namespace at once. If an engineer has a binding that allows reading secrets, they can pull the TLS keys. If they have permissions for pod subresources like pod exec or pod logs, they can bypass the route. They can log straight into the container or read raw app output from the API server.

OpenShift RBAC: architecture patterns and best practices

Continue reading? Get the full guide.

Free. No spam. Unsubscribe anytime.

What native route encryption solves and what it leaves open

An openshift reencrypt route protects data in transit from network sniffers on the wire. It proves the identity of both the public router and the internal backend pod. It also lets the router add HTTP headers before sending traffic to the app. This satisfies strict audit rules that ban plain text traffic inside the cluster network.

Still, route encryption and static RBAC roles only decide how traffic flows and who logs in. They do not inspect what individual commands or queries do during an active engineer session. Once a developer has pod exec permissions to fix a broken route, they have full shell control. Native RBAC cannot approve a single command or rewrite sensitive fields like emails, phone numbers, or card numbers in flight.

Govern kubectl and API calls in flight

Identity providers and Kubernetes RBAC decide who logs into a cluster. They cannot redact keys inside returned JSON objects or hold a risky delete call for review. By design, hoop.dev runs as an open-source proxy, a sidecar for your Kubernetes API, checking requests and responses without replacing RBAC.

First, hoop.dev guardrails refuse banned methods, paths, or headers before they run. Next, hoop.dev data masking rewrites sensitive keys in returned Secret, ConfigMap, and log responses in memory, and writes each decision to the audit trail. Explore the repo on GitHub.

Frequently asked questions

What is the difference between reencrypt and passthrough routes?

A reencrypt route decrypts traffic at the router and encrypts it again before reaching the pod. A passthrough route sends encrypted traffic straight to the pod without decrypting it at the router.

Why does a reencrypt route need two certificates?

The router needs one public certificate to serve outside users over the internet. It also needs a destination CA certificate to verify the internal TLS certificate on the pod.

Can RBAC deny rules block engineers from viewing route secrets?

No, because permissions in Kubernetes RBAC are purely additive and include no deny rules. To block secret access, you must grant a smaller Role that leaves out secret read permissions.

The query runs. The emails stay hidden.