Skip to content

Releases: aws/aws-application-networking-k8s

Release v1.1.6

16 Oct 21:57

Choose a tag to compare

Release v1.1.6 adds support for Additional Tags on VPC Lattice Resources

What's Changed

  • Add Support for Additional Tags on VPC Lattice Resources @SinghVikram97 in #829
  • Minor dependency upgrades

Full Change log: v1.1.5...v1.1.6

Release v1.1.5

30 Sep 02:48

Choose a tag to compare

Release v1.1.5 adds support for Standalone Service Creation

What's Changed

Full Changelog: v1.1.4...v1.1.5

Release v1.1.4

15 Aug 17:17

Choose a tag to compare

Release v1.1.4 includes the following improvements.

What's Changed

  • Address Multi-Cluster Health Check Configuration Inconsistency by @rlymbur in #789
  • Correct additional target group creation when using the ExportedPorts field with HTTPRoutes by @rlymbur in #709

Full Change log: v1.1.3...v1.1.4

Release v1.1.3

11 Jul 13:38

Choose a tag to compare

Release v1.1.3 includes minor dependency upgrades and test improvements.

What's Changed

  • Minor dependency upgrades
  • Added integration test and additional logging around pod IP updates by @rlymbur in #771
  • Address Access Log Subscription Test Failures by @rlymbur in #772

Full Changelog: v1.1.2...v1.1.3

Release v1.1.2

05 Jun 21:00

Choose a tag to compare

Release v1.1.2 enables controller gRPC ServiceExport and includes security fixes.

What's Changed

  • Add TLSRoute Hostname Validation (#736)
  • Fix panic on AccessLogPolicy targetRef namespace mismatch (#739)
  • Update deploy.md (#737)
  • Support gRPC ServiceExport (#756)

Miscellaneous and Security fixes

  • Potential fix for code scanning alert no. 1: Workflow does not contain permissions (#743)
  • Fix for Dependabot configuration (#744)
  • Correct Dependabot to run "make presubmit" before creating PRs (#758)

Full Changelog: v1.1.1...v1.1.2

Release v1.1.1

14 May 22:34
dee091e

Choose a tag to compare

Release v1.1.1 improves controller setup and adds the ability to manually specify priority configuration in HTTPRoute resources.

What's Changed

  • Added support for make setup to automate controller setup (#702)
  • Addressed failing E2E tests (#703)
  • Added GitHub Merge Queue support (#707)
  • Gateways not managed by the controller are now ignored (#709)
  • Added support for priority configuration in HTTPRoute resources (#734)

Notable Dependency Upgrades

  • Go version to 1.23.6 (#717)

Document Improvements

  • Noted north/south traffic restrictions (#723)
  • Fixed general formatting issues (#726)
  • Updated issue templates

Full Change log: v1.1.0...v1.1.1

Release v1.1.0

18 Dec 23:20

Choose a tag to compare

Breaking Changes

Gateway API GRPCRoute version v1alpha2 removal

Release v1.1 of the AWS Gateway API Controller is built against Gateway API v1.2. The controller is also compatible with Gateway API v1.1 but not with v1.0.

  • Upgrade to v1.2 of gateway API (#680)

We strongly recommend backing up your configuration as this transition particularly affects GRPCRoute in the following ways:

  • The controller requires either Gateway API v1.1 or v1.2 to be installed.
  • If using Gateway API v1.1, existing GRPCRoutes on v1alpha2 will automatically update to v1 when the controller reconciles them.
  • Alternatively, you can manually update your GRPCRoute versions.
  • Kubernetes will reject new GRPCRoute objects created using v1alpha2.

If you are upgrading to Gateway API v1.2, you will need to take additional steps because v1alpha2 is no longer a valid version for GRPCRoute objects. For detailed instructions, refer to the v1.2 Gateway API release notes.

To ensure a streamlined Gateway API migration, follow the guide to upgrade the controller from v.1.0.x to v1.1.y

Document Improvements

  • Document updates for Gateway API v1.2 CRDs (#683)
  • Upgrading to Gateway API v1.2

Full Change log: v1.0.7...v1.1.0

Release v1.0.7

05 Nov 23:51

Choose a tag to compare

Release v1.0.7 improves route reconciliation performance via configurable max workers for route controller instances. Also improves debugging by enabling correlation of log lines using unique reconciliation IDs. Finally, includes documentation improvements and Helm chart enhancements.

What's Changed

  • Add Trace IDs and metadata to better correlate log lines for a single reconciliation (#648)
  • Add DISABLE_TAGGING_SERVICE_API environment variable to helm chart (#655)
  • Add PodDisruptionBudget and topologySpreadConstraints to helm chart (#651)
  • Add configurable max workers for route controller instances (#672)

Documentation Improvements

  • Minor fixes for typos and version numbers (#654, #662, #664)

Full Change log: v1.0.6...v1.0.7

Log Lines

Example new log lines including trace ID, start with reconcile_start and end with reconcile_end:

2024-11-01T15:30:40.995-0700	INFO	controller.route	gwlog/metadata.go:76	reconcile_start	{"type": "route", "name": "drift-5-nwppj20ozc", "namespace": "e2e-test", "trace_id": "1d3cb3c5-c8e1-4c2f-b313-4a19c6f85e6d"} 2024-11-01T15:30:40.995-0700	INFO	controller.route	controllers/route_controller.go:275	Found aws-vpc-lattice for Route for drift-5-nwppj20ozc, e2e-test	{"trace_id": "1d3cb3c5-c8e1-4c2f-b313-4a19c6f85e6d"} 2024-11-01T15:30:40.995-0700	INFO	controller.route	controllers/route_controller.go:190	reconcile, deleting	{"name": "drift-5-nwppj20ozc", "trace_id": "1d3cb3c5-c8e1-4c2f-b313-4a19c6f85e6d"} 2024-11-01T15:30:40.995-0700	INFO	controller.route	gateway/model_build_lattice_service.go:140	No custom-domain-name for route drift-5-nwppj20ozc-e2e-test	{"trace_id": "1d3cb3c5-c8e1-4c2f-b313-4a19c6f85e6d"} 2024-11-01T15:30:41.495-0700	INFO	controller.route	lattice/service_manager.go:353	Success DeleteService svc-012345012345012345	{"trace_id": "1d3cb3c5-c8e1-4c2f-b313-4a19c6f85e6d"} 2024-11-01T15:30:41.524-0700	INFO	controller.route	controllers/route_controller.go:202	reconciled	{"name": "drift-5-nwppj20ozc", "trace_id": "1d3cb3c5-c8e1-4c2f-b313-4a19c6f85e6d"} 2024-11-01T15:30:41.556-0700	INFO	controller.route	gwlog/metadata.go:82	reconcile_end	{"type": "route", "name": "drift-5-nwppj20ozc", "namespace": "e2e-test", "trace_id": "1d3cb3c5-c8e1-4c2f-b313-4a19c6f85e6d"} 

Release v1.0.6

14 Jun 23:18

Choose a tag to compare

This release introduces support for TLSRoute, allowing users to set up TLS passthrough network connectivity.

What's Changed

  • Added support for clusters running in private VPCs (#627)
  • Added support for TLSRoute and TLS passthrough, please check the user guide for more it's details. (#634)
  • Added TLSRoute and TLS passthrough document (#650)

NOTICE

The release v1.0.6 introduced a new TLSRoute CRD, it is already included the controller v1.0.6 helm chart. If you do not use the helm install to install the v1.0.6 controller, please make sure to manually install the TLSRoute CRD in your k8s cluster.

Full Change log: v1.0.5...v1.0.6

Release v1.0.5

09 May 17:54

Choose a tag to compare

Release v1.0.5 adds logic to conditionally inject the pod readiness gates and adde support for attaching TargetGroupPolicy to ServiceExport objects.

What's Changed

  • Added logic to conditionally inject pod readiness gates (#629)
  • Added support for attaching Target Group policies to ServiceExport objects (#622)

Document Improvements

  • Reorganized and refactored documentations (#630)

Full Change log: v1.0.4...v1.0.5