-
Notifications
You must be signed in to change notification settings - Fork 141
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
Voyager unable to update haproxy.cfg - must have at most 1048576 characters #1553
Comments
We have 1.460 configured backends in ingress - 99% look like this: - host: example.com
http:
paths:
- backend:
headerRules:
- X-Forwarded-Host %[req.hdr(Host)]
- X-Forwarded-Port %[dst_port]
- X-Forwarded-Proto https if { ssl_fc }
serviceName: our-service
servicePort: 80
path: / Voyager generated haproxy.cfg with 2.917 backends - 99 % like this:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We're currently use appscode/voyager:v11.0.1.
When updating ConfigMap with haproxy.cfg Voyager Operator reports
Failed to process key default/ingress. Reason: ConfigMap "voyager-ingress" is invalid: []: Too long: must have at most 1048576 characters
I'll check if Custom Templates can help reduce haproxy.cfg size.
Is there any other workaround?
Thank you
The text was updated successfully, but these errors were encountered: