Describe the problem
Not sure what to say. Please consider supporting IPv6, spend hours to try to make it work in an ipv6-only kubernetes (with helm chart) cluster. As far as I can tell by now I would need to derive a docker image to overwrite the nginx config as there is a convoluted script /app/bin/start which generates the symlinked config (which makes it not easily overwritable by configmap) based of some django template... this seems excessive to enable basic IPv6 connectivity.
Solution brainstorm
Have at the minimum nginx bind to [::]. gunicorn binds to 127.0.0.1 which should be working as long as nginx is binding also to [::]. In theory the internal communication can also be safely switched to [::1].
Maybe i missed some obvious solution but if not: other then the technical solution i wondering why this is still across many projects a missing "feature". e.g. is it missing info/knowledge, missing test infra, missing ...?
Describe alternatives you have considered
Tried to:
- ConfigMap Overwrite
/etc/nginx/sites-enabled/web.conf -> application error as it can't write the config file as it is read-only this way
- ConfigMap Overwrite
/app/bin/start with a version which sed's the nginx listen directive with a [::]:8080 -> container does not start permission denied, probably because its not executable marked after configmap mount
- Searched for a "BIND" Environment variable
- Overwrite GUNICORN Environment variable -> turned out to be wrong approach as its anyway "just" internal communication, env variable seemed to also have no effect
- some other stuff
Screenshots
No response
Additional context
No response
Describe the problem
Not sure what to say. Please consider supporting IPv6, spend hours to try to make it work in an ipv6-only kubernetes (with helm chart) cluster. As far as I can tell by now I would need to derive a docker image to overwrite the nginx config as there is a convoluted script
/app/bin/startwhich generates the symlinked config (which makes it not easily overwritable by configmap) based of some django template... this seems excessive to enable basic IPv6 connectivity.Solution brainstorm
Have at the minimum nginx bind to [::]. gunicorn binds to 127.0.0.1 which should be working as long as nginx is binding also to [::]. In theory the internal communication can also be safely switched to [::1].
Maybe i missed some obvious solution but if not: other then the technical solution i wondering why this is still across many projects a missing "feature". e.g. is it missing info/knowledge, missing test infra, missing ...?
Describe alternatives you have considered
Tried to:
/etc/nginx/sites-enabled/web.conf-> application error as it can't write the config file as it is read-only this way/app/bin/startwith a version whichsed's the nginx listen directive with a[::]:8080-> container does not start permission denied, probably because its not executable marked after configmap mountScreenshots
No response
Additional context
No response