Cloud Foundry on Kubernetes brings power and portability, but routing traffic into your workloads is where the game is won or lost. Ingress is more than a component — it’s the gate, the selector, and the first security layer for every request. Done right, it delivers seamless, scalable, secure access. Done wrong, it means downtime and frustration.
Kubernetes Ingress for Cloud Foundry combines the declarative power of Kubernetes with the developer‑first platform Cloud Foundry has always been known for. It translates high-level networking rules into the low-level realities of load balancing, SSL termination, and path-based routing. This lets you control exactly how traffic reaches applications, whether you’re handling a single microservice or a federation of them.
The most common pattern uses an Ingress Controller such as NGINX or Contour to route HTTP(S) traffic to Cloud Foundry workloads running in Kubernetes pods. Operators create Kubernetes Ingress resources, mapping hostnames and paths to services backing Cloud Foundry apps. Certificates can be automated with cert-manager, keeping the security tight and the operational overhead low. Integration with Kubernetes RBAC means platform teams can limit who can change routing rules, without slowing down deployment workflows.