consul/website/content/docs/release-notes/consul-api-gateway/v0_5_x.mdx

---
layout: docs
page_title: 0.5.x
description: >-
  Learn about the changes to Consul API Gateway in version 0.5.x, including support for Consul Dataplane, routing to services in peered clusters, distroless Envoy containers, and Kubernetes tolerations
---

# Consul API Gateway 0.5.0

We are pleased to announce the following updates to Consul API Gateway. 

## Release highlights

- **Consul Dataplane Support:** Consul 1.14 introduces a simplified deployment architecture that eliminates the need to deploy node-level Consul clients on Kubernetes. This is referred to as Consul Dataplane. API Gateway 0.5.0 supports this type of deployment.

- **Routing to Services in Peered Clusters:** API Gateway now supports the ability to route traffic to services that are imported from peered Consul clusters. Cluster peering is was added in Consul 1.14. Refer to the `MeshService` [documentation](/consul/docs/api-gateway/configuration/meshservice) for additional information.

- **Deploy in Admin Partitions:** API Gateway can now be deployed in any Consul admin partition. Previous versions of API Gateway could only be deployed in the default partition. The partition is configured in the `GatewayClassConfig`.

- **Configure Maximum Incoming Connections:** You can now configure the number of concurrent incoming connections that Envoy will allow. This is configured by setting the value of the `maxConnection` parameter in the `GatewayClassConfig`.

- **Distroless Envoy Containers:** API Gateway now uses the `envoy-distroless` container image of the Envoy proxy. This improves the security of a gateway by reducing the attack surface of Envoy. Consul Helm chart `1.0.0` or greater is required to use the distroless container image.

- **Support for Kubernetes Tolerations:** You can now configure toleration settings for the Consul API Gateway controller and Gateway instances made with the managed gateway class directly from the [Helm chart](/consul/docs/k8s/helm#h-apigateway). Kubernetes toleration settings allow you to control which nodes in a K8s cluster that the API Gateway pods should be deployed on. Refer to  [Taints and Tolerations](https://kubernetes.io/docs/concepts/scheduling-eviction/taint-and-toleration/) in the Kubernetes documentation for more information. 

## Supported software

- Consul 1.12.0+
- HashiCorp Consul Helm chart:
  - 0.49.1+ for Consul 1.12 - 1.13
  - 1.0.0+ for Consul 1.14+
- Kubernetes 1.21+
  - Kubernetes 1.25 is not supported at this time.
- Kubectl 1.21+
- Envoy proxy support is determined by the Consul version deployed. Refer to [Envoy Integration](/consul/docs/connect/proxies/envoy) for details.

## Kubernetes Gateway API specification

Supported version of the [Gateway API](https://gateway-api.sigs.k8s.io/) spec: v0.5.0

## Upgrading

For detailed information on upgrading, please refer to the [Upgrades page](/consul/docs/api-gateway/upgrades)

## Known issues
At the time of release, there are no known issues in API Gateway v0.5.0


## Changelogs

The changelogs for this major release version and any maintenance versions are listed below.

~> **Note:** The following link will take you to the changelogs on the GitHub website.

- [0.5.0](https://github.com/hashicorp/consul-api-gateway/releases/tag/v0.5.0)