Skip to content

Release v1.0.0
Compare
Choose a tag to compare
@mikhail-aws mikhail-aws released this 18 Nov 03:30
· 70 commits to main since this release
v1.0.0
f69e34c
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

What's Changed

On behalf of the entire AWS Gateway API Controller team, we are pleased to announce the GA release of the AWS Gateway API Controller v1.0.0. A big thank you to all the contributors that made this release possible.

This release completes the VPC Lattice resource ownership changes by removing the Service Network conflict which enables advanced multi-cluster setups. We also added support for the recent GA release of the Gateway API v1 CRDs.

Highlights

  • Detached Gateway from VPC Lattice service network, removing service network conflict (#480, #504)
  • Added DEFAULT_SERVICE_NETWORK environment variable that will automatically create a service network and its VPC association at the controller startup (#502)
  • Updated RouteRules to return 404 status code for invalid backendRefs (#497)
  • Added handling of resource status for TargetGroupPolicy (#509)
  • Updated controller dependencies to [email protected] / [email protected] (#503)

Breaking Changes

IAM Policies

  • The required IAM policies have changed - tag:GetResources policy is now required for running the controller. Please update your existing service account with the new policy provided in examples/recommended-inline-policy.json.

Gateway/VPCAssociationPolicy

  • Creating a Gateway no longer creates a service network and its VPC association. Please refer to the documentation for more details. Existing service networks and their associations will not be deleted.
  • Deprecated Gateway’s application-networking.k8s.aws/lattice-vpc-association annotation. Instead, use VPCAssociationPolicy CRD to configure an association.
  • Added ownership concept to VPCAssociationPolicy. It will no longer delete VPC associations that are not owned by the controller.

TargetGroupPolicy

  • Updated the CRD. The new version of controller requires the updated version of TargetGroupPolicy CRD.

General Improvements

  • Fixed e2e tests and examples to be compatible with Gateway API v1 CRDs (#515)
  • Added TargetGroupPolicy controller for updating resource status (#509)
  • Target group reconciliation performance improvements (#495, #501)
  • IAMAuthPolicy E2E test improvements (#496)
  • Target de-registration E2E test improvements (#491)
  • General E2E test performance improvements (#510)

Documentation Improvements

  • Updated deployment instructions (#511, #512, #516)
  • Replaced API references to automatically generated docs from CRDs (#505, #507)
  • Updated and reorganized documentation structure (#506, #513, #517, #521, #522)
  • Added API references to Gateway, xRoute, Service, and IAMAuthPolicy (#492, #500, #514, #518)

Upgrade Instructions

  • TargetGroupPolicy CRD is updated. This is bundled with deploy-*.yaml and Helm chart, but you can also find the CRD on config/crds/bases/application-networking.k8s.aws_targetgrouppolicies.yaml.
  • If you are upgrading from versions older than v0.0.18, please also check v0.0.18 release notes for more feature updates and breaking changes.

Full Changelog: v0.0.18...v1.0.0

Assets 2
Loading