Add to local deployment (kind) the standalone console UI

[eranra]

No description provided.

[eranra]

@jpinsonneau ^^

[jpinsonneau]

@eranra what about having all the time the standalone page hosted in the console plugin pod ? 😸
So you will be able to open the page from a specific route or use the plugin if available.

[eranra]

@jpinsonneau ^^^ this is an interesting thought ... what about authentication/security... is there a need for more work so this route will be secured somehow ???

[jpinsonneau]

Yes this need additional authentication work on standalone page + backend and maybe more to define who can access.

Currently, if you access pod service (only within cluster by default), you access all our backend api.
For example forward plugin service using oc port-forward service/network-observability-plugin 9001:9001 -n network-observability
Then you can run queries like:
https://localhost:9001/api/loki/flows?filters=&limit=100&reporter=both&timeRange=300

There are no auth / token check since a proxy is automatically generated by console between plugin and the service: /api/proxy/plugin/<plugin-name>/<proxy-alias>/<request-path>?<optional-query-parameters>

[jotak]

Side note: in my README rewritting PR ( https://github.com/netobserv/network-observability-operator/pull/125/files#diff-b335630551682c19a781afebcf4d07bf978fb1f8ac04c6bf87428ed5106870f5R72 ) , I've left some space to mention the standalone console. I think it would be great to deploy it, not only for local deployment on kind, but more generally when the openshift console is not available. It's aligned with what Julien suggested, I guess.