After upgrading OpenShift Logging from 5.x to 6.2, the Observability Operator must be installed to enable the Logs Console plugin (logging-view-plugin).

In environment where the Console Operator configuration is managed via GitOps (ArgoCD).

After installing the Observability Operator, we observed that the logging-view-plugin gets enabled temporarily but is automatically disabled after an ArgoCD sync or redeployment. This happens because the Observability Operator and the GitOps-managed Console configuration both attempt to manage the same Console resource, causing a conflict.

Expected Documentation Improvement

Existing Doc: https://docs.redhat.com/en/documentation/red_hat_openshift_cluster_observability_operator/1-latest/html/ui_plugins_for_red_hat_openshift_cluster_observability_operator/logging-ui-plugin#coo-logging-ui-plugin-install_logging-ui-plugin 

The documentation should clearly mention that when the Console configuration is managed using automation or GitOps tools (such as ArgoCD), the logging-view-plugin must be explicitly defined in the Console resource to ensure it persists across syncs.

As documented in the following KB article:
KB: https://access.redhat.com/solutions/7128832 

To prevent the plugin from being disabled after a GitOps sync, the Console configuration managed by ArgoCD must include:

$ oc get console.operator cluster -o yaml

apiVersion: operator.openshift.io/v1
kind: Console
metadata:
  name: cluster
spec:
  plugins:
    - logging-view-plugin    <---