Add Support for Priority Configuration in HTTPRoute Resource #734
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
Feature
Which issue does this PR fix:
#719
What does this PR do / Why do we need it:
This adds support for a custom annotation on HTTPRoutes to manually assign a priority for a rule. You can manually assign priorities to rules using the custom annotation
application-networking.k8s.aws/rule-{index}-priority.Testing done on this change:
Automation added to e2e:
test/suites/integration/httproute_rule_priority_test.gowas added to confirm manually assigned priorities are reflected on VPC Lattice resources correctly.Will this PR introduce any new dependencies?:
No.
Will this break upgrades or downgrades. Has updating a running cluster been tested?:
No, this change is backwards compatible with existing routes.
Does this PR introduce any user-facing change?:
Do all end-to-end tests successfully pass when running
make e2e-test?:By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.