You may encounter a problem where the Konvoy Ops Portal is suddenly not accessible after creating an ingress object that does not specify an HTTP path.
Doing this will capture all other HTTP paths and override existing ingress rules, which can result in the Ops Portal and all other app dashboards breaking.
If you notice that your Ops Portal is suddenly inaccessible, a first troubleshooting step could be to check for recently created ingress objects:
If there is a rule that redirects port 80 or 443 traffic to "path: /" or that does not specify a path, then this rule is to blame for the problem with the Ops Portal.
Other ingress paths that can cause problems in a Konvoy cluster include:
Either remove the ingress or specify a different HTTP path to resolve this.
Doing this will capture all other HTTP paths and override existing ingress rules, which can result in the Ops Portal and all other app dashboards breaking.
If you notice that your Ops Portal is suddenly inaccessible, a first troubleshooting step could be to check for recently created ingress objects:
kubectl get ingress --all-namespaces
If there is a rule that redirects port 80 or 443 traffic to "path: /" or that does not specify a path, then this rule is to blame for the problem with the Ops Portal.
Other ingress paths that can cause problems in a Konvoy cluster include:
/token /dex /ops/portal/kibana /konvoy/api-server /ops/portal/kubernetes /ops/portal /ops/landing /ops/portal/grafana /ops/portal/alertmanager /ops/portal/prometheus /_oauth /ops/portal/traefik
Either remove the ingress or specify a different HTTP path to resolve this.