Gateway API on Our Managed Kubernetes Platform

Our Managed Kubernetes platform supports the Gateway API – a modern and flexible way to manage ingress and traffic routing in Kubernetes.

You can either use Cilium as your Gateway API provider out of the box or install any other compatible implementation you prefer.
The platform does not require you to use a specific Gateway API provider. You have full control over which implementation you use.

What Is Gateway API?

Gateway API is a native Kubernetes API that standardises how traffic enters and moves through a cluster. It is meant to be the long-term replacement for the traditional Ingress API.
Compared to Ingress, Gateway API provides:

• A role-oriented model (cluster operators, platform admins, application owners)
• Clear separation between infrastructure (Gateways) and routing rules (Routes)
• First-class support for advanced use cases such as:
  • Multiple listeners (HTTP, HTTPS, TCP, TLS)
  • Cross-namespace routing
  • Fine-grained traffic policies
• A provider-agnostic contract, allowing multiple implementations to coexist

Thanks to these improvements, more teams are choosing the Gateway API as their preferred way of managing traffic in Kubernetes.

Responsibilities and Operational Model

Cluster Administrator Responsibilities

Gateway API uses Custom Resource Definitions (CRDs) that work with all implementations.
The cluster administrator is responsible for:

• Installing the Gateway API CRDs
• Upgrading the Gateway API CRDs when required
• Ensuring CRD versions are compatible with the chosen provider

Managing the CRD lifecycle is kept separate from installing providers. This helps prevent unexpected changes across your cluster.

Using Cilium as a Gateway API Provider

If you decide to use Cilium as your Gateway API provider, follow these steps:

1. Prerequisites required in the Cilium configuration are already considered by us.
2. The following Gateway API CRDs must be installed. Please follow the instructions for installing the gateway CRDs according to Cilium’s Gateway API documentation.
   • Make sure the version of the Gateway API CRDs you chose to install is compatible with the installed Cilium version in your cluster.
3. After installing the Gateway API CRDs, you need to restart the Cilium Components using the following commands:

kubectl -n kube-system rollout restart deployment/cilium-operator 
kubectl -n kube-system rollout restart ds/cilium

Since you are managing the Gateway APIs, it is important to consider these items:

1. Once in a while, we will update Cilium and will announce it to our customers.
   • Do not forget to update CRDs after Cilium Upgrades if it is required.
2. Configure Cilium Gateway resources according to your traffic requirements.

For detailed installation steps, configuration options, and supported Gateway API features, see the official Cilium documentation.

Using Other Gateway API Providers

If you choose another Gateway API provider, you need to follow their documentation accordingly. Check the provider’s documentation for details on supported features, limitations, and how to upgrade. not modify or restrict third-party Gateway API providers.

Summary

• Gateway API is the modern, extensible successor to Ingress. Our platform supports the Gateway API in a provider-agnostic manner.
• Customers remain free to choose and operate alternative implementations.
• Cilium is fully managed and supported as a Gateway API provider.
• Cluster administrators manage Gateway API CRDs.This approach gives you flexibility, follows standards, and ensures long-term compatibility with Kubernetes.