Closed erikfuller closed 2 months ago
For large cluster, to improve the performance and we can annotate or add finalizer to the service used by Lattice HTTPRoute/GRPCRoute/ServiceExport. With annotation or finalizer, the controller do not need loop through them during creation of a Pod
Thanks for bringing this up. I've opened https://github.com/aws/aws-application-networking-k8s/issues/631 to track these improvements.
What type of PR is this? bug fix
Which issue does this PR fix:
623
What does this PR do / Why do we need it: Validates the pod requires the readiness gate before adding it. Readiness gates are added to pods where
Under these conditions, it is assumed the pod will be a member of a Lattice target group and the readiness gate is added. All other pods will not receive the readiness gate.
Other minor issues addressed:
mapper.go
androute_controller.go
mutating_handler.go
Testing done on this change: Added extensive unit tests on the logic.
Automation added to e2e: Updated the webhook e2e tests to include a full test where we check the readiness gate is added and transitions to "ready". Note this test takes a little under 2m to run.
Also Ran the regular e2e-tests just to make sure my small refactoring didn't break anything.
Will this PR introduce any new dependencies?: No
Will this break upgrades or downgrades. Has updating a running cluster been tested?: No
Does this PR introduce any user-facing change?: No, bug fix.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.