-
Notifications
You must be signed in to change notification settings - Fork 201
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
scale-server-slots on Ingress resource is ignored #670
Comments
Hi @mike-code , Could you check if you have any of the legacy annotation |
The ConfigMap (created by helm chart) is empty |
Hi @mike-code |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
@hdurand0710 I don't have any "legacy" configuration, ie. this is a fresh haproxy ingress instance from latest helm chart. btw. Is is possible to reduce the default http backends from 42 to 1? The excessive number of "virtual" backends pollutes the metrics with backend that'll never be running. |
@mike-code Scale the Info:
I was not able to reproduce. So, in order to try to reproduce and solve your issue, could you send me:
Thanks for your help. |
@hdurand0710
Is this expected? |
I could not reproduce this.
When you scale from "2" to "5", it's expected that you get an number of SRV_X >= number of pods, with the number of SRV_X being a multiple of the |
appVersion: 3.0.1
Using the following
Ingress
the backend still scales to
42
.The text was updated successfully, but these errors were encountered: