Contour is a Kubernetes ingress controller using Envoy proxy.
We are delighted to present version v1.29.0 of Contour, our layer 7 HTTP reverse proxy for Kubernetes clusters.
A big thank you to everyone who contributed to the release.
As of this release, Contour now uses the envoy
xDS server implementation by default. This xDS server implementation is based on Envoy's go-control-plane project and will eventually be the only supported xDS server implementation in Contour. This change is expected to be transparent to users.
If you encounter any issues, you can easily revert to the contour
xDS server with the following configuration:
(if using Contour config file)
server:
xds-server-type: contour
(if using ContourConfiguration CRD)
...
spec:
xdsServer:
type: contour
You will need to restart Contour for the changes to take effect.
(#6146, @skriss)
Contour no longer informs on v1beta1 resources that have graduated to v1. This includes the "core" resources GatewayClass, Gateway, and HTTPRoute. This means that users should ensure they have updated CRDs to Gateway API v1.0.0 or newer, which introduced the v1 version with compatibility with v1beta1.
(#6153, @sunjayBhatia)
Contour now uses the Kubernetes EndpointSlices API by default to determine the endpoints to configure Envoy, instead of the Endpoints API. Note: if you need to continue using the Endpoints API, you can disable the feature flag via featureFlags: ["useEndpointSlices=false"]
in the Contour config file or ContourConfiguration CRD.
(#6149, @izturn)
It's possible that multiple HTTPRoutes will define the same Match conditions. In this case the following logic is applied to resolve the conflict:
With above ordering, any HTTPRoute that ranks lower, will be marked with below conditions accordionly
Accepted: True
and PartiallyInvalid: true
Conditions and Reason: RuleMatchPartiallyConflict
.Accepted: False
Condition and Reason RuleMatchConflict
.(#6188, @lubronzhan)
As described in Envoy documentations, spawn_upstream_span
should be true when envoy is working as an independent proxy and from now on contour tracing spans will show up as a parent span to upstream spans.
(#6271, @SamMHD)
envoyproxy/ratelimit
image tag to 19f2079f
, for multi-arch support and other improvements. (#6246, @skriss)envoy
go-control-plane xDS server, use a separate snapshot cache for Endpoints, to minimize the amount of unnecessary xDS traffic generated. (#6250, @skriss)0s
disables the timeout. (#6375, @skriss)--disable-feature
flags on Contour Deployment for each disabled feature. Previously a comma separated list was passed which was incorrect. (#6413, @sunjayBhatia)Contour can no longer be configured with a GatewayClass controller name (gateway.controllerName in the config file or ContourConfiguration CRD), as the config field has been removed. Instead, either use a specific Gateway reference (gateway.gatewayRef), or use the Gateway provisioner.
(#6145, @skriss)
As of this release, the contour
xDS server implementation is now deprecated. Once the go-control-plane based envoy
xDS server has had sufficient production bake time, the contour
implementation will be removed from Contour. Notification of removal will occur at least one release in advance.
(#6146, @skriss)
Contour now uses the EndpointSlices API by default, and its usage of the Endpoints API is deprecated as of this release. Support for Endpoints, and the associated useEndpointSlices
feature flag, will be removed in a future release.
(#6149, @izturn)
For a fresh install of Contour, consult the getting started documentation.
To upgrade an existing Contour installation, please consult the upgrade documentation.
Contour v1.29.0 is tested against Kubernetes 1.27 through 1.29.
We’re immensely grateful for all the community contributions that help make Contour even better! For this release, special thanks go out to the following contributors:
If you're using Contour and want to add your organization to our adopters list, please visit this page. If you prefer to keep your organization name anonymous but still give us feedback into your usage and scenarios for Contour, please post on this GitHub thread.
We are delighted to present version v1.28.4 of Contour, our layer 7 HTTP reverse proxy for Kubernetes clusters.
0s
now disables the timeout (#6379).For a fresh install of Contour, consult the getting started documentation.
To upgrade an existing Contour installation, please consult the upgrade documentation.
Contour v1.28.4 is tested against Kubernetes 1.27 through 1.29.
If you're using Contour and want to add your organization to our adopters list, please visit this page. If you prefer to keep your organization name anonymous but still give us feedback into your usage and scenarios for Contour, please post on this GitHub thread.
We are delighted to present version v1.27.3 of Contour, our layer 7 HTTP reverse proxy for Kubernetes clusters.
For a fresh install of Contour, consult the getting started documentation.
To upgrade an existing Contour installation, please consult the upgrade documentation.
Contour v1.27.3 is tested against Kubernetes 1.26 through 1.28.
If you're using Contour and want to add your organization to our adopters list, please visit this page. If you prefer to keep your organization name anonymous but still give us feedback into your usage and scenarios for Contour, please post on this GitHub thread.
We are delighted to present version v1.29.0-rc.1 of Contour, our layer 7 HTTP reverse proxy for Kubernetes clusters.
A big thank you to everyone who contributed to the release.
Please note that this is pre-release software, and as such we do not recommend installing it in production environments. Feedback and bug reports are welcome!
As of this release, Contour now uses the envoy
xDS server implementation by default. This xDS server implementation is based on Envoy's go-control-plane project and will eventually be the only supported xDS server implementation in Contour. This change is expected to be transparent to users.
If you encounter any issues, you can easily revert to the contour
xDS server with the following configuration:
(if using Contour config file)
server:
xds-server-type: contour
(if using ContourConfiguration CRD
...
spec:
xdsServer:
type: contour
You will need to restart Contour for the changes to take effect.
(#6146, @skriss)
Contour no longer informs on v1beta1 resources that have graduated to v1. This includes the "core" resources GatewayClass, Gateway, and HTTPRoute. This means that users should ensure they have updated CRDs to Gateway API v1.0.0 or newer, which introduced the v1 version with compatibility with v1beta1.
(#6153, @sunjayBhatia)
Contour now uses the Kubernetes EndpointSlices API by default to determine the endpoints to configure Envoy, instead of the Endpoints API. Note: if you need to continue using the Endpoints API, you can disable the feature flag via featureFlags: ["useEndpointSlices=false"]
in the Contour config file or ContourConfiguration CRD.
(#6149, @izturn)
It's possible that multiple HTTPRoutes will define the same Match conditions. In this case the following logic is applied to resolve the conflict:
With above ordering, any HTTPRoute that ranks lower, will be marked with below conditions accordionly
Accepted: True
and PartiallyInvalid: true
Conditions and Reason: RuleMatchPartiallyConflict
.Accepted: False
Condition and Reason RuleMatchConflict
.(#6188, @lubronzhan)
As described in Envoy documentations, spawn_upstream_span
should be true when envoy is working as an independent proxy and from now on contour tracing spans will show up as a parent span to upstream spans.
(#6271, @SamMHD)
envoyproxy/ratelimit
image tag to 19f2079f
, for multi-arch support and other improvements. (#6246, @skriss)envoy
go-control-plane xDS server, use a separate snapshot cache for Endpoints, to minimize the amount of unnecessary xDS traffic generated. (#6250, @skriss)0s
disables the timeout. (#6375, @skriss)Contour can no longer be configured with a GatewayClass controller name (gateway.controllerName in the config file or ContourConfiguration CRD), as the config field has been removed. Instead, either use a specific Gateway reference (gateway.gatewayRef), or use the Gateway provisioner.
(#6145, @skriss)
As of this release, the contour
xDS server implementation is now deprecated. Once the go-control-plane based envoy
xDS server has had sufficient production bake time, the contour
implementation will be removed from Contour. Notification of removal will occur at least one release in advance.
(#6146, @skriss)
Contour now uses the EndpointSlices API by default, and its usage of the Endpoints API is deprecated as of this release. Support for Endpoints, and the associated useEndpointSlices
feature flag, will be removed in a future release.
(#6149, @izturn)
The simplest way to install v1.29.0-rc.1 is to apply one of the example configurations:
With Gateway API:
kubectl apply -f https://raw.githubusercontent.com/projectcontour/contour/v1.29.0-rc.1/examples/render/contour-gateway.yaml
Without Gateway API:
kubectl apply -f https://raw.githubusercontent.com/projectcontour/contour/v1.29.0-rc.1/examples/render/contour.yaml
Contour v1.29.0-rc.1 is tested against Kubernetes 1.27 through 1.29.
We’re immensely grateful for all the community contributions that help make Contour even better! For this release, special thanks go out to the following contributors:
If you're using Contour and want to add your organization to our adopters list, please visit this page. If you prefer to keep your organization name anonymous but still give us feedback into your usage and scenarios for Contour, please post on this GitHub thread.
We are delighted to present version v1.28.3 of Contour, our layer 7 HTTP reverse proxy for Kubernetes clusters.
See the release notes for v1.29.3 here.
Note that this Envoy version retains the hop-by-hop TE header when set to trailers
, fixing a regression seen in v1.29.0-v1.29.2 for HTTP/2, particularly gRPC. However, this version of Contour continues to set the envoy.reloadable_features.sanitize_te
Envoy runtime setting to false
to ensure seamless upgrades. This runtime setting will be removed in Contour v1.29.0.
See the release notes for v1.21.9 here.
For a fresh install of Contour, consult the getting started documentation.
To upgrade an existing Contour installation, please consult the upgrade documentation.
Contour v1.28.3 is tested against Kubernetes 1.27 through 1.29.
If you're using Contour and want to add your organization to our adopters list, please visit this page. If you prefer to keep your organization name anonymous but still give us feedback into your usage and scenarios for Contour, please post on this GitHub thread.
We are delighted to present version v1.27.2 of Contour, our layer 7 HTTP reverse proxy for Kubernetes clusters.
For a fresh install of Contour, consult the getting started documentation.
To upgrade an existing Contour installation, please consult the upgrade documentation.
Contour v1.27.2 is tested against Kubernetes 1.26 through 1.28.
If you're using Contour and want to add your organization to our adopters list, please visit this page. If you prefer to keep your organization name anonymous but still give us feedback into your usage and scenarios for Contour, please post on this GitHub thread.
We are delighted to present version v1.26.3 of Contour, our layer 7 HTTP reverse proxy for Kubernetes clusters.
For a fresh install of Contour, consult the getting started documentation.
To upgrade an existing Contour installation, please consult the upgrade documentation.
Contour v1.26.3 is tested against Kubernetes 1.26 through 1.28.
If you're using Contour and want to add your organization to our adopters list, please visit this page. If you prefer to keep your organization name anonymous but still give us feedback into your usage and scenarios for Contour, please post on this GitHub thread.
We are delighted to present version v1.28.2 of Contour, our layer 7 HTTP reverse proxy for Kubernetes clusters.
See the release notes here.
Note that this Envoy version reverts the HTTP/2 codec back to nghttp2
from oghttp2
.
As of version v1.29.0, Envoy removes the hop-by-hop TE header.
However, this causes issues with HTTP/2, particularly gRPC, with implementations expecting the header to be present (and set to trailers
).
Contour disables this via Envoy runtime setting and reverts to the v1.28.x and prior behavior of allowing the header to be proxied.
Once this Envoy PR that enables the TE header including trailers
to be forwarded is backported to a release or a new minor is cut, Contour will no longer set the aforementioned runtime key.
For a fresh install of Contour, consult the getting started documentation.
To upgrade an existing Contour installation, please consult the upgrade documentation.
Contour v1.28.2 is tested against Kubernetes 1.27 through 1.29.
If you're using Contour and want to add your organization to our adopters list, please visit this page. If you prefer to keep your organization name anonymous but still give us feedback into your usage and scenarios for Contour, please post on this GitHub thread.
We are delighted to present version v1.28.1 of Contour, our layer 7 HTTP reverse proxy for Kubernetes clusters.
For a fresh install of Contour, consult the getting started documentation.
To upgrade an existing Contour installation, please consult the upgrade documentation.
Contour v1.28.1 is tested against Kubernetes 1.27 through 1.29.
If you're using Contour and want to add your organization to our adopters list, please visit this page. If you prefer to keep your organization name anonymous but still give us feedback into your usage and scenarios for Contour, please post on this GitHub thread.
We are delighted to present version v1.27.1 of Contour, our layer 7 HTTP reverse proxy for Kubernetes clusters.
For a fresh install of Contour, consult the getting started documentation.
To upgrade an existing Contour installation, please consult the upgrade documentation.
Contour v1.27.1 is tested against Kubernetes 1.26 through 1.28.
If you're using Contour and want to add your organization to our adopters list, please visit this page. If you prefer to keep your organization name anonymous but still give us feedback into your usage and scenarios for Contour, please post on this GitHub thread.