This repository has been archived by the owner on Mar 19, 2024. It is now read-only.
Releases: hashicorp/consul-api-gateway
Releases · hashicorp/consul-api-gateway
v0.5.5
v0.5.4
v0.5.3
v0.5.2
v0.5.1
v0.5.0
0.5.0 (November 17, 2022)
FEATURES:
- Switch deployed gateways to use TTL-based health checks to better support running with Consul servers that are not on the same network as a gateway [GH-371]
IMPROVEMENTS:
- Add optional
consul.partition
andconsul.serverName
to GatewayClassConfig CRD. If set these will be used to initialize the partition and server name used in TLS verification for communicating with Consul in a deployment. [GH-450] - Add optional
podSecurityPolicy
to GatewayClassConfig CRD. If set and "managed" ServiceAccounts are being used, a Role and RoleBinding are created to attach the namedPodSecurityPolicy
to the managed ServiceAccount. [GH-433] - Add optional configuration for maximum upstream connections to GatewayClassConfig CRD. If unset, behavior is unchanged and Envoy's default will be used. [GH-405]
- Add support for tolerations to Consul API Gateway Controller and GatewayClassConfig. [GH-426]
- Integrate consul-server-connection-manager to support Agentless consul server discovery [GH-449]
- Support distroless Envoy images (with continued support for distroful images) [GH-391]
- api: add OpenAPI schema and stubs for bootstrap token CRUD [GH-384]
- go: update to Go v1.19 [GH-424]
- makefile: switch back to upstream go-changelog repo [GH-385]
BUG FIXES:
- Delete gateway ACL tokens on shutdown so they are not orphaned after being provisioned at startup. [GH-377]
- Fix failing root certificate watch for controller when deployed in secondary federated datacenter. [GH-368]
- When a gateway is created in a namespace that doesn't exist in Consul and namespace mirroring is enabled, create the namespace in Consul. [GH-397]
NOTES:
- RefNotPermitted error is now returned instead of InvalidCertificateRef in the case where a cross namespace certificate is not allowed by a ReferenceGrant [GH-412]
v0.4.0
0.4.0 (August 16, 2022)
DEPRECATIONS:
- gateway-api: ReferencePolicy is deprecated and will be removed in a future release. The functionally identical ReferenceGrant should be used instead. [GH-224]
FEATURES:
- Assign BackendNotFound reason to ResolvedRefs condition on routes where the backend reference is a supported kind but does not exist [GH-291]
- Assign InvalidKind reason to ResolvedRefs condition on routes where the backend reference is an unknown or unsupported kind [GH-290]
- Support prefix replacement URLRewrite filter (docs) [GH-282]
- gateway-api: update to the v0.5.0-rc1 release with v1beta1 resource support [GH-224]
- gateway-api: update to the v0.5.0-rc2 release with v1beta1 resource support [GH-279]
- gateway-api: update to the v0.5.0 release with v1beta1 resource support [GH-283]
BUG FIXES:
v0.3.0
0.3.0 (June 21, 2022)
BREAKING CHANGES:
- Gateway listener
certificateRefs
to secrets in a different namespace now require a ReferencePolicy [GH-154]
FEATURES:
- Added a new configuration option called deployment to GatewayClassConfig that allows the user to configure the number of instances that are deployed per gateway. [GH-195]
- Define anti-affinity rules so that the scheduler will attempt to evenly spread gateway pods across all available nodes [GH-202]
IMPROVEMENTS:
- go: build with Go 1.18 [GH-167]
- k8s/controllers: watch for ReferencePolicy changes to reconcile and revalidate affected Gateways [GH-207]
BUG FIXES:
- Clean up stale routes from gateway listeners when not able or allowed to bind, to prevent serving traffic for a detached route. [GH-197]
- Clean up stale routes from gateway listeners when route no longer references the gateway. [GH-200]
- Fix SPIFFE validation for connect certificates that have no URL (e.g., Vault connect certificates) [GH-225]
- Properly handle re-registration of deployed gateways when an agent no longer has the gateway in its catalog [GH-227]
NOTES:
- Gateway IP address assignment logic updated to include the case when multiple different pod IPs exist [GH-201]
v0.2.1
v0.2.0
0.2.0 (April 27, 2022)
BREAKING CHANGES:
- Routes now require a ReferencePolicy to permit references to services in other namespaces. [GH-143]
IMPROVEMENTS:
- changelog: add go-changelog templates and tooling [GH-101]
- k8s/controllers: watch for ReferencePolicy changes to reconcile and revalidate affected HTTPRoutes [GH-156]
- k8s/controllers: watch for ReferencePolicy changes to reconcile and revalidate affected TCPRoutes [GH-162]
BUG FIXES: