Skip to content
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

Allow to configure LoadBalancerClass for service in gateway helm chart #39079

Closed
Legion2 opened this issue May 21, 2022 · 2 comments
Closed

Allow to configure LoadBalancerClass for service in gateway helm chart #39079

Legion2 opened this issue May 21, 2022 · 2 comments
Labels
area/environments area/networking kind/enhancement lifecycle/automatically-closed Indicates a PR or issue that has been closed automatically. lifecycle/stale Indicates a PR or issue hasn't been manipulated by an Istio team member for a while

Comments

@Legion2
Copy link

Legion2 commented May 21, 2022

Describe the feature request
I want to set the spec.loadBalancerClass of the Service in the gateway helm chart, see Specifying class of load balancer implementation.

Describe alternatives you've considered
Use annotations on the Service to select load balancer implementation.

Affected product area (please put an X in all that apply)

[ ] Docs
[x] Installation
[x] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

Affected features (please put an X in all that apply)

[ ] Multi Cluster
[ ] Virtual Machine
[ ] Multi Control Plane

Additional context
The AWS Load Balancer Controller supports this field to select the load balancer controller instead of the in-tree controller. The spec.loadBalancerClass field was added in kubernetes v1.22.

@howardjohn
Copy link
Member

We cannot add an option for every single field in Kubernetes to the charts. If you want to configure advanced fields, i recommend following steps like https://docs.solo.io/gloo-edge/latest/installation/gateway/kubernetes/helm_advanced/

@istio-policy-bot
Copy link

🚧 This issue or pull request has been closed due to not having had activity from an Istio team member since 2022-05-23. If you feel this issue or pull request deserves attention, please reopen the issue. Please see this wiki page for more information. Thank you for your contributions.

Created by the issue and PR lifecycle manager.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/environments area/networking kind/enhancement lifecycle/automatically-closed Indicates a PR or issue that has been closed automatically. lifecycle/stale Indicates a PR or issue hasn't been manipulated by an Istio team member for a while
Projects
None yet
Development

No branches or pull requests

3 participants