-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
remove load-balancer-controller and ingress tests #225
Conversation
32d30bb
to
49956cf
Compare
✔️ Change looks good! 🥐 Re-running flaky tests. |
I think we should add some context to the commit messages here - I can see what they're doing, but it's unclear what the motivation is. |
|
Suggest that we squash these three commits together with a commit message something like:
( |
8fd9a68
to
e54f46d
Compare
We've decided to remove non-critical addons from this module #224. Rather than try to provide a one-size-fits-all setup, we're changing focus to provide a minimal setup, and expect that users will use another mechanism for additional configuration.
e54f46d
to
898d907
Compare
@aidy sure makes sense - could you check the latest squashed commit |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚀
* These tags were previously required by aws-load-balancer-controller/alb-ingress-controller * We no longer ship a ingress controller with the module since #225 * aws-load-balancer-controller doesn't need those tags anyway since v2.1.2 - kubernetes-sigs/aws-load-balancer-controller#1773
* These tags were previously required by aws-load-balancer-controller/alb-ingress-controller * We no longer ship a ingress controller with the module since #225 * aws-load-balancer-controller doesn't need those tags anyway since v2.1.2 - kubernetes-sigs/aws-load-balancer-controller#1773
Contributes #224