alert-exabyte-15243
01/17/2024, 3:09 PMaverage-finland-92144
01/17/2024, 3:26 PMalert-exabyte-15243
01/17/2024, 3:27 PMaverage-finland-92144
01/17/2024, 3:29 PM<https://Ingress-IP/console>
? is that where you get the 404?alert-exabyte-15243
01/17/2024, 3:31 PMkubectl get ingress -n flyte
gives an IP address, accessing it with both http/https gives Nginx's 404average-finland-92144
01/17/2024, 3:31 PMkubectl get pods -n flyte
alert-exabyte-15243
01/17/2024, 3:33 PMkubectl get pods -n flyte
NAME READY STATUS RESTARTS AGE
datacatalog-75bf86bb9d-fswrs 1/1 Running 0 144m
flyte-pod-webhook-776c7bc497-p6dws 1/1 Running 0 144m
flyteadmin-fc9dbf4bc-lc4lj 1/1 Running 0 144m
flyteconsole-75b675c6b5-ds5f4 1/1 Running 0 144m
flytepropeller-d5878f847-twhjv 1/1 Running 0 144m
flytescheduler-5589cdfd8f-8tkhz 1/1 Running 0 144m
syncresources-9b5687f84-5j2c7 1/1 Running 0 144m
average-finland-92144
01/17/2024, 3:36 PMalert-exabyte-15243
01/17/2024, 3:41 PMcan you try with a local DNS entry?absolutely; could you please elaborate on how to get one?
average-finland-92144
01/17/2024, 3:43 PMhosts
file in your OS. Like described here (see step 11)alert-exabyte-15243
01/17/2024, 4:02 PM/console
uri is accessible (but jumping between pages doesn't work ofc, leading to localhost addresses).alert-exabyte-15243
01/17/2024, 4:02 PMaverage-finland-92144
01/17/2024, 4:35 PM<your-Ingress-IP> <your-Ingress-host>
alert-exabyte-15243
01/17/2024, 4:58 PMaverage-finland-92144
01/17/2024, 4:59 PM