Skip to content

[BUG]: 404 errors after setup due to failed ingress deploy #3

@ericsmalling

Description

@ericsmalling

Is there an existing issue for this?

  • I have searched the existing issues

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:

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.

Steps To Reproduce

See above

Additional Information

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions