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 | ||
|---|---|---|---|---|
|
||||
|
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, GKE Gateway controller, 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. |
|
GKE Gateway controller requires vendor-specific custom resources for health checks and, for HA controllers, session affinity. For details, refer to GKE Gateway controller custom resources. |