Description of problem:

• In a context where the logging-view-plugin is deployed and the TroubleshootingPanel plugin is missing, the console still proxies traffic to a non-existent korrel8r service, as seen below: 

$ oc -n openshift-console logs console-55bdc6c988-wh6qc | grep logging-view-plugin
2025-09-22T11:12:14.509597231Z I0922 11:12:14.506333       1 main.go:219]  - logging-view-plugin
2025-09-22T11:12:14.677673390Z I0922 11:12:14.676255       1 server.go:550]  - /api/proxy/plugin/logging-view-plugin/backend/ -> https://logging-loki-gateway-http.openshift-logging.svc.cluster.local:8080
2025-09-22T11:12:14.677673390Z I0922 11:12:14.676287       1 server.go:550]  - /api/proxy/plugin/logging-view-plugin/korrel8r/ -> https://korrel8r.openshift-operators.svc.cluster.local:9443

$ oc -n openshift-operators get svc korrel8r
No resources services.core found in openshift-operators namespace. 

Version-Release number of selected component (if applicable):

• Cluster Observability Operator v1.2.1
• Openshift Logging version 6.1.7

Actual results:

• The above manifests as a permission denied and we suspect it's leading to arbitrary and transient (i.e. the issue goes away after 30-60 seconds, without customer intervention) "Missing permissions to get logs" in a customer environment.

Expected results:

• For the console plugin to not proxy traffic to a non-existent service, when the TroubleshootingPanel plugin is not provisioned.

Additional info:

• The "Missing permissions to get logs" is also rather ambiguous in this case and we see no trace of it that can lead to a conclusive root cause: as such, it could also benefit of additional verbosity to facilitate troubleshooting similar situations in the future.