We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Occasionally, the webadmin app returns a 404 error after initial setup becuase the ingress did not deploy successfully.
In this case, the setup.sh output usually contains:
Error from server (InternalError): error when creating "webadmin_svc_ingress.yaml": Internal error occurred: failed calling webhook "validate.nginx.ingress.kubernetes.io": failed to call webhook: Post "https://ingress-nginx-controller-admission.ingress-nginx.svc:443/networking/v1/ingresses?timeout=10s": dial tcp 10.96.212.95:443: connect: connection refused
Re-deploying the ingress via kubectl apply -f webadmin_svc_ingress.yaml -n secure usually resolves this.
kubectl apply -f webadmin_svc_ingress.yaml -n secure
See above
No response
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Is there an existing issue for this?
Description of the bug
Occasionally, the webadmin app returns a 404 error after initial setup becuase the ingress did not deploy successfully.
In this case, the setup.sh output usually contains:
Re-deploying the ingress via
kubectl apply -f webadmin_svc_ingress.yaml -n secure
usually resolves this.Steps To Reproduce
See above
Additional Information
No response
The text was updated successfully, but these errors were encountered: