As discussed in this slack thread the NetObserv console UI is accessing the loki-frontend pods directly going around the loki-gateway. This makes it so when the loki-operator runs with Network policies enabled (default in 4.20+) it has to create a dedicated network policy that exposes the loki-frontend HTTP port to any pod, increasing the attack vector. Originally this was done as Loki Operator didn't provide a way for clients to know some details, however with the more recent versions of Loki Operator it seems that this information is now present in the status of the LokiStack. The goal of this issue is to see if it's possible for the console UI to stop probing the loki-frontend pod and instead use the LokiStack status

—

Here is the current controller implementation reading LokiStack:

https://github.com/netobserv/network-observability-operator/blob/main/internal/pkg/manager/status/status_manager.go#L199

From there, we should:

• Improve LokiStack reading to cover all the cases
• Send the config / issues to the console plugin pod through the configmap
• Refactor the error display
• Remove the status endpoint