Kubernetes Gateway API supported implementations

1 minute read
CloudBees Beta

This feature is available as a beta release and is subject to change without notice. CloudBees recommends stringent testing in a development environment and a complete review of the documentation and architecture before using it in production.

Modern Cloud Platforms

This content applies only to CloudBees CI on modern cloud platforms.

CloudBees CI on modern cloud platforms uses Kubernetes Gateway API resources to manage ingress routing. Gateway API is an open standard, and CloudBees CI is designed to work with any conformant implementation that meets the requirements described in Verify Kubernetes Gateway API prerequisites.

Tested implementations

CloudBees validates the following Gateway API implementations with CloudBees CI:

Implementation Project Validated by CloudBees

Istio does not currently provide native support Gateway API session persistence (GEP-1619) for High Availability (HA) or High Scalability (HS) controllers. You must create an Istio DestinationRule with consistentHash based on an HTTP cookie to enable sticky sessions.

Other conformant implementations

Any Gateway API implementation that has achieved conformance status works with CloudBees CI, provided it meets the prerequisites. This includes implementations such as NGINX Gateway Fabric, Traefik, Contour, Cilium, and HAProxy Ingress.

For the full and up-to-date list of conformant implementations, refer to the Gateway API implementations documentation.

Conformant implementations that CloudBees has not tested may be compatible, but compatibility is not guaranteed. If you encounter issues with a specific implementation, contact CloudBees Support; however, issues specific to the Gateway implementation may require support from your Gateway vendor.