-
Notifications
You must be signed in to change notification settings - Fork 350
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
bug: apisix-gateway port 443 can't listening #2093
Labels
bug
Something isn't working
Comments
Same here, when i learn the official docs:https://apisix.apache.org/zh/docs/ingress-controller/tutorials/mtls/ it say i should set |
@Revolyssup please help to look |
I am already tracking this. this is doc related issue |
Completed by #2085 |
github-project-automation
bot
moved this from 🏗 In progress
to ✅ Done
in Apache APISIX backlog
Jan 16, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Current Behavior
apisix-gateway port 443 can't listening
Expected Behavior
kubectl get svc -n apisix
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
apisix-admin ClusterIP 10.0.155.67 9180/TCP 23m
apisix-dashboard ClusterIP 10.0.217.115 80/TCP 23m
apisix-etcd ClusterIP 10.0.237.167 2379/TCP,2380/TCP 23m
apisix-etcd-headless ClusterIP None 2379/TCP,2380/TCP 23m
apisix-gateway NodePort 10.0.39.237 80:30693/TCP 23m
apisix-ingress-controller ClusterIP 10.0.217.232 80/TCP 23m
Error Logs
warn api/server.go:76 failed to load x509 key pair, will not start admission server {"Error": "open /etc/webhook/certs/cert.pem: no such file or directory", "CertFilePath": "/etc/webhook/certs/cert.pem", "KeyFilePath": "/etc/webhook/certs/key.pem"}
Steps to Reproduce
helm install apisix apisix/apisix --create-namespace --namespace apisix --set dashboard.enabled=true --set ingress-controller.enabled=true --set gateway.tls.enabled=true --set ingress-controller.config.apisix.serviceNamespace=apisix
Environment
apisix 3.6.0
kubectl version
Client Version: v1.28.2
Kustomize Version: v5.0.4-0.20230601165947-6ce0bf390ce3
Server Version: v1.26.6
The text was updated successfully, but these errors were encountered: