From ae028bfea8742cf559d2948f8524dec52141c272 Mon Sep 17 00:00:00 2001 From: Michael Burke Date: Wed, 9 Jul 2025 17:53:44 -0400 Subject: [PATCH] [enterprise-4.19] Need to add colon and remove bold object names from documentation --- .../logging-6.0/log6x-upgrading-to-6.adoc | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/observability/logging/logging-6.0/log6x-upgrading-to-6.adoc b/observability/logging/logging-6.0/log6x-upgrading-to-6.adoc index 468a3849ea8e..da5e9306c635 100644 --- a/observability/logging/logging-6.0/log6x-upgrading-to-6.adoc +++ b/observability/logging/logging-6.0/log6x-upgrading-to-6.adoc @@ -24,40 +24,40 @@ include::modules/log6x-oc-explain.adoc[leveloffset=+1] == Log Storage -The only managed log storage solution available in this release is a Lokistack, managed by the *loki-operator*. This solution, previously available as the preferred alternative to the managed Elasticsearch offering, remains unchanged in its deployment process. +The only managed log storage solution available in this release is a Lokistack, managed by the Loki-operator. This solution, previously available as the preferred alternative to the managed Elasticsearch offering, remains unchanged in its deployment process. [IMPORTANT] ==== -To continue using an existing Red Hat managed Elasticsearch or Kibana deployment provided by the *elasticsearch-operator*, remove the owner references from the `Elasticsearch` resource named `elasticsearch`, and the `Kibana` resource named `kibana` in the `openshift-logging` namespace before removing the `ClusterLogging` resource named `instance` in the same namespace. +To continue using an existing Red Hat managed Elasticsearch or Kibana deployment provided by the Elasticsearch Operator, remove the owner references from the `Elasticsearch` resource named `elasticsearch`, and the `Kibana` resource named `kibana` in the `openshift-logging` namespace before removing the `ClusterLogging` resource named `instance` in the same namespace. ==== -. Temporarily set *ClusterLogging* to state `Unmanaged` +. Temporarily set `ClusterLogging` resource to the `Unmanaged` state by running the following command: + [source,terminal] ---- $ oc -n openshift-logging patch clusterlogging/instance -p '{"spec":{"managementState": "Unmanaged"}}' --type=merge ---- -. Remove *ClusterLogging* `ownerReferences` from the *Elasticsearch* resource +. Remove the `ownerReferences` parameter from the `Elasticsearch` resource by running the following command: + -The following command ensures that *ClusterLogging* no longer owns the *Elasticsearch* resource. Updates to the *ClusterLogging* resource's `logStore` field will no longer affect the *Elasticsearch* resource. +The following command ensures that Cluster Logging no longer owns the `Elasticsearch` resource. Updates to the `ClusterLogging` resource's `logStore` field will no longer affect the `Elasticsearch` resource. + [source,terminal] ---- $ oc -n openshift-logging patch elasticsearch/elasticsearch -p '{"metadata":{"ownerReferences": []}}' --type=merge ---- -. Remove *ClusterLogging* `ownerReferences` from the *Kibana* resource +. Remove the `ownerReferences` parameter from the `Kibana` resource. + -The following command ensures that *ClusterLogging* no longer owns the *Kibana* resource. Updates to the *ClusterLogging* resource's `visualization` field will no longer affect the *Kibana* resource. +The following command ensures that Cluster Logging no longer owns the `Kibana` resource. Updates to the `ClusterLogging` resource's `visualization` field will no longer affect the `Kibana` resource. + [source,terminal] ---- $ oc -n openshift-logging patch kibana/kibana -p '{"metadata":{"ownerReferences": []}}' --type=merge ---- -. Set *ClusterLogging* to state `Managed` +. Set the `ClusterLogging` resource to the `Managed` state by running the following command: + [source,terminal] ----