What's Changed
New feature
- Add TargetGroupPolicy CRD that allows granular upstream network configuration #349 #357 #361
- GRPCRoute support #341 #350
- GRPCRoute with ServiceImport as backendRef is not supported yet - only single cluster use case is supported at the moment.
- Add support to route requests by HTTP method #332
- Add support for IPv6 automatically if your EKS cluster supports IPv6 (documentation) #329
- Allow configurable ports for HTTPRoute, GRPCRoute BackendRef ports and ServiceExport port using annotations #335 #351
- Increase name length limit for generated VPC Lattice TargetGroups #357
General Improvement and bug fixes
- Fixed bug that was deleting ServiceNetworkServiceAssociations for shared accounts #356
- Refactor k8s resource event handling and service reconciler #360
- Added HTTPRoute Creation/Update E2E Tests #312
- E2E test framework improvement, shorten the whole e2etest suite time #330 #344
- Remove aws-sdk override, use vpc lattice sdk directly from aws-sdk-go #320
- Log improvement, migrate to zap logger and make log to be more clear #318
- Quote accountId in Helm chart ConfigMap #333
- Refactor service_manager.go #345
- Mock IMDS in controller config tests #338
Upgrade Instructions
- If you have installed the controller manually, make sure to install below CRDs in your cluster before running the upgraded controller. The CRDs are located at:
- TargetGroupPolicy - config/crds/bases/application-networking.k8s.aws_targetgrouppolicies.yaml
- GRPCRoute - config/crds/bases/k8s-gateway-v0.6.1.yaml
- IAM policy required for the controller’s serviceaccount has been changed; it now requires ec2:DescribeTags permission. Please review the new permissions in examples/recommended-inline-policy.json and update the service account if needed.
Breaking Changes
- If using a multi-cluster environment, make sure to update all controllers in the environment to v0.0.16. The naming scheme has been changed for VPC Lattice target groups generated by the controller. When the controller is upgraded, it will automatically create new target groups and replace old ones with them. Due to this change, v0.0.16 controllers will not be able to recognize ServiceImports created from controllers with version v0.0.15 or lower, and vice versa.
New Contributors
- @rlymbur made their first contribution in #311
- @csantanapr made their first contribution in #333
- @erikfuller made their first contribution in #332
- @klyubin made their first contribution in #338
Full Changelog: v0.0.15...v0.0.16