[BUG] There is no projects in my console UI

[StreamSun]

Describe the bug

Expected behavior

There is no projects in my console UI when I deploy it use flyte-core, but if I use flyte-binary to show the projects, it works

Additional context to reproduce

No response

Screenshots

No response

Are you sure this issue hasn't been raised already?

• Yes

Have you read the Code of Conduct?

• Yes

[welcome]

Thank you for opening your first issue here! 🛠

[punkerpunker]

I am experiencing exact same issue. flyte-binary works, flyte-core - emtpy.

[davidmirror-ops]

@StreamSun @punkerpunker what flyte and flytekit versions are you using? Is this flyte-core deployment behind a proxy?
There's the initialProjects setting which is particular to flyte-core, please check if it's there in your config.

[punkerpunker]

Hey @davidmirror-ops, thanks for the quick reply. I've deployed flyte-core following your guide, using helm chart with the following version:

- name: flyte-core
  version: 1.14.1
  repository: https://flyteorg.github.io/flyte

If that helps - I've also checked postgres - project table isn't empty:

root@postgres-8b6895f5c-cdpjd:/# psql -U flyte -d flyte
psql (13.5 (Ubuntu 13.5-0ubuntu0.21.04.1))
Type "help" for help.

flyte=# select * from projects;
 id |          created_at           |          updated_at           | deleted_at |  identifier   |     name      |        description        |                   labels                   | state 
----+-------------------------------+-------------------------------+------------+---------------+---------------+---------------------------+--------------------------------------------+-------
  1 | 2025-01-09 16:50:42.739772+00 | 2025-01-09 16:50:42.739772+00 |            | flytesnacks   | flytesnacks   | flytesnacks description   |                                            |     0
  2 | 2025-01-09 16:50:42.743719+00 | 2025-01-09 16:50:42.743719+00 |            | flytetester   | flytetester   | flytetester description   |                                            |     0
  3 | 2025-01-09 16:50:42.746655+00 | 2025-01-09 16:50:42.746655+00 |            | flyteexamples | flyteexamples | flyteexamples description |                                            |     0
  4 | 2025-01-09 17:15:28.266146+00 | 2025-01-09 17:15:28.266146+00 |            | gleb          | gleb          | gleb                      | \x0a04676c65621204676c65622204676c65622a00 |     0
(4 rows)

However, any call to UI returns 304 and keeps showing empty interface, even if following the direct link to the run given by pyflyte.

If that helps - I can try running another version of flyte-core. Deployment is not behind the proxy, it is port-forwarded via kubectl.

Thank you!

[punkerpunker]

@davidmirror-ops
As frontend is communicating to the FlyteAdmin with the ADMIN_API_URL provided by configmap, we need to modify it for the sandbox installation so it communicates to it via port-forwarded loopback.

To avoid CORS issues, we also need to modify adminServer allowedOrigins.

See the following PR: davidmirror-ops/flyte-the-hard-way#24

[davidmirror-ops]

Yeah, this is very likely a CORS issue. See #5855