Release notes

Review the release notes for kgateway. For a detailed list of changes between tags, use the GitHub Compare changes tool.

v2.3.0

🔥 Breaking changes

🌟 New features

Control plane changes

• Common labels: Add custom labels to all resources that are created by the Helm charts by using the commonLabels field, including the Deployment, Service, and ServiceAccount of the control plane. This allows you to better organize your resources or integrate with external tools. For more information, see Common labels.
• PriorityClass support: Assign a PriorityClassName to control plane pods using the controller.priorityClassName Helm field. Priority indicates the importance of a pod relative to other pods and allows higher priority pods to preempt lower priority ones when scheduling.
• Topology spread constraints: Distribute kgateway controller pods across failure domains such as zones or nodes by using the topologySpreadConstraints Helm field. For more information, see Topology spread constraints.

Static IPs for Gateways

Assign a static IP address to the Kubernetes service that exposes your Gateway using the spec.addresses field with type: IPAddress.

For more information, see Static IP address.

Local rate limit filter options

The TrafficPolicy resource now supports the percentEnabled and percentEnforced optional fields to control the percentage of requests for which the local rate limit filter is enabled or enforced. If not set, both fields default to 100, which enables and enforces the local rate limiting filter for 100% of all requests.

Use these fields for gradual rollouts or to run the filter in shadow mode (percentEnabled: 100, percentEnforced: 0), where rate limiting statistics are collected without blocking any requests.

For more information, see Gradual rollout and shadow mode.

Gateway proxy customization

The GatewayParameters resource now supports gateway proxy customization via overlay fields. Overlays use strategic merge patch (SMP) semantics to apply advanced customizations to the Kubernetes resources that are generated for gateway proxies, including the Service, ServiceAccount, and Deployment.

The following overlays are supported:

• Use deploymentOverlay, serviceOverlay, and serviceAccountOverlay to patch the generated Deployment, Service, and ServiceAccount.
• Use horizontalPodAutoscaler, verticalPodAutoscaler, and podDisruptionBudget to automatically create and configure these resources targeting the proxy Deployment.

For more information, see Change proxy settings and Overlay examples.