Bram van Meurs
10/12/2023, 8:34 AM404 Not Found
error in the browser console (see screenshot).
About the config:
• using the flyte-core helmchart
• ingress and auth are not yet enabled
• deployed in a non standard namespace
• port forwarding to the flyteadmin svc (k port-forward svc/flyteadmin 8080:80
) and running curl <http://localhost:8080/api/v1/projects>
works fine and shows a newly created project (with flytectl).
I checked all pod logs and they seem fine (other than the same 404 not found on the console logs).
Any idea where to look for the issue? How is the console trying to get the projects? Through flyteadmin?Bram van Meurs
10/12/2023, 8:36 AMBram van Meurs
10/12/2023, 9:15 AMYee
Bram van Meurs
10/17/2023, 5:04 PMDerek Yu
12/28/2023, 5:50 PMflyteconsole
, with the console unable to fetch data. Wondering what you did to get the port forwarding to work? Thanks!Yee
avesuni
01/04/2024, 4:41 PMingress.enabled: false
). We have an Istio Gateway behind Google application loadbalancer, but at this point I'd just like to get port-forwarding to the Admin console working. I get the same Not found
message whether I'm using port-forwarding or Istio's virtual service. Any help would be much appreciated. Logs showing nothing like with Bram.Fabio Grätz
01/04/2024, 5:12 PMFabio Grätz
01/04/2024, 5:13 PMavesuni
01/04/2024, 6:38 PMport-forward svc/flyteadmin -n flyte 8080:80
and kubectl port-forward svc/flyteadmin -n flyte 8081:81
Wow that's a complicated virtualservice manifest 😅 Let me try itavesuni
01/04/2024, 6:43 PMFabio Grätz
01/04/2024, 6:44 PM