-
Notifications
You must be signed in to change notification settings - Fork 21
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
ADR for extending Istio CR with support for AWS LB type #1117
base: main
Are you sure you want to change the base?
Conversation
awsLoadBalancerType: nlb | ||
``` | ||
|
||
* When switching to NLB Istio Module operator should apply additionally the following `serviceAnnotations` with Istio Operator Manifest: |
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.
What about this warning in the AWS load balancer controller docs:
It's not recommended to modify or add the service.beta.kubernetes.io/aws-load-balancer-type annotation on an existing Service resource. If a change is desired, delete the existing Service resource and create a new one instead of modifying an existing Service.
If you modify this annotation on an existing Service resource, you might end up with leaked LBC resources.
see https://kubernetes-sigs.github.io/aws-load-balancer-controller/v2.10/guide/service/nlb/
It looks like it would be better to create bew services for each LB type.
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.
lets discuss on Monday, how we are going to approach this. Since downtime is a thing to consider.
Co-authored-by: Tim Riffer <tim.riffer@gmx.de>
Description
Changes proposed in this pull request:
Pre-Merge Checklist
Related issues