Introduce aws-load-balancer-controller #198
Merged
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 of your changes
This PR introduces aws load-balancer controller in the mix. In-tree providers like used here are subject to being removed in the near future.
In order to more realistically picture a production setup, i also chose to switch to an Ingress instead of a plain service.
I updated to latest version of uptest because debugging with old kuttl was close to impossible and in order to use latest pod identity standard it was necessary to update the eks-module which meant i needed to upgrade every other configuration dependency as well, so please pardon that i mix these changes in one PR.
I also moved the composition to
apis/pat
to comply with current standards.I have:
make reviewable
to ensure this PR is ready for review.backport release-x.y
labels to auto-backport this PR, as appropriate.How has this code been tested