You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Enabling TLS on the ingress-controller gateway service (apisix-ingress-controller-apisix-gateway) doesn't make the pod listen on port 9443.
This causes refused connections since the LoadBalancer's public IP doesn't have anywhere to connect:
curl: (7) Failed to connect to test-apisix.example.com port 443 after 262 ms: Connection refused
Configured ingress-controller as an apisix subchart, but the same applies for the standalone chart:
ingress-controller:
enabled: true
config:
# misconfig due to a hardcoded value https://github.com/apache/apisix-helm-chart/issues/774
httpListen: ":9080"
ingressPublishService: "ingress-apisix/apisix-ingress-controller-apisix-gateway"
apisix:
adminAPIVersion: "v3"
existingSecret: "admin-creds"
existingSecretAdminKeyKey: "admin"
gateway:
type: LoadBalancer
externalTrafficPolicy: Local
tls:
enabled: true <== DOESN'T WORK
Only the HTTP port (9080) is specified in the deployment.yamltemplate and there's no optional setting for the TLS port like the apisix chart's template.
The only place that the tls key is used is in the etcd server sidecar here, which also looks a bit mistakenly copied.
The text was updated successfully, but these errors were encountered:
Enabling TLS on the
ingress-controller
gateway service (apisix-ingress-controller-apisix-gateway
) doesn't make the pod listen on port 9443.This causes refused connections since the LoadBalancer's public IP doesn't have anywhere to connect:
Configured
ingress-controller
as anapisix
subchart, but the same applies for the standalone chart:Only the HTTP port (9080) is specified in the
deployment.yaml
template and there's no optional setting for the TLS port like theapisix
chart's template.The only place that the
tls
key is used is in theetcd
server sidecar here, which also looks a bit mistakenly copied.The text was updated successfully, but these errors were encountered: