[feat: gw api] Add a utility to implement Gateway API spec to generate relevant Kubernetes objects for a Gateway #4107
+3,516
−66
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.
Description
See inline comments for further details. The goal of this PR is to introduce a utility that we can call from a reconcile controller that will generate a complete resource map. This is the general flow
reconciler detects changed gateway -> reconciler invokes route utility to get complete resource picture [we are here] -> translator translate k8s objects into a common format -> deployer takes the common format and materializes the elbv2 objects based off the common format.
Checklist
README.md
, or thedocs
directory)BONUS POINTS checklist: complete for good vibes and maybe prizes?! 🤯