Nicolfo commented on issue #11974: URL: https://github.com/apache/apisix/issues/11974#issuecomment-2663700115
For future reference Thanks to @juzhiyuan i was able to find a related issue https://github.com/apache/apisix/issues/4942 TLDR: There are two possible ways to fix my problem: - use the servless-pre-function plugin to add x-forworded-port: 443 header to every request (i didn't tested this solution because it doesn't look clean to me) - set the pod to run on the 443 port instead, this can be done by adding two configuration in the helm values ```yaml apisix: ssl: enabled: true containerPort: 443 ... podSecurityContext: sysctls: - name: net.ipv4.ip_unprivileged_port_start value: "1" ``` (the podSecurityContext enable the pod to use the 443 port, which is forbidden by default) Honestly, I don't see why this isn't the default, especially in a Helm-installed environment. This seems like the expected behavior for most users. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
