此内容没有您所选择的语言版本。

Chapter 1. Uninstalling logging


1.1. Uninstalling the Red Hat OpenShift Logging Operator

You can uninstall Red Hat OpenShift Logging Operator by using either the OpenShift CLI (oc) or the Red Hat OpenShift Logging web console.

Delete the Red Hat OpenShift Logging Operator by using the OpenShift CLI (oc).

Prerequisites

  • You have administrator permissions.
  • You installed the OpenShift CLI (oc).

Procedure

  1. Delete the ClusterLogForwarder custom resource (CR) by running the following command:

    $ oc delete ClusterLogForwarder instance -n openshift-logging
    Copy to Clipboard Toggle word wrap

    Change instance to the name of your ClusterLogForwarder CR if you have used a different name.

  2. Delete the service account by running the following commands:

    $ oc adm policy remove-cluster-role-from-user lokistack-tenant-logs -z logging-collector -n openshift-logging
    Copy to Clipboard Toggle word wrap
    $ oc adm policy remove-cluster-role-from-user collect-application-logs -z logging-collector -n openshift-logging
    Copy to Clipboard Toggle word wrap
    $ oc adm policy remove-cluster-role-from-user collect-infrastructure-logs -z logging-collector -n openshift-logging
    Copy to Clipboard Toggle word wrap
    $ oc adm policy remove-cluster-role-from-user collect-audit-logs -z logging-collector -n openshift-logging
    Copy to Clipboard Toggle word wrap
    $ oc adm policy remove-cluster-role-from-user logging-collector-logs-writer -z logging-collector -n openshift-logging
    Copy to Clipboard Toggle word wrap
    $ oc delete serviceaccount logging-collector -n openshift-logging
    Copy to Clipboard Toggle word wrap
  3. Delete the LogFileMetricExporter resource if you have deployed it by running the following command:

    $  oc -n openshift-logging delete LogFileMetricExporter --all
    Copy to Clipboard Toggle word wrap
  4. Check the current version of the subscribed Red Hat OpenShift Logging Operator in the currentCSV field by running the following command:

    $ oc get csv -n openshift-logging | grep cluster-logging
    Copy to Clipboard Toggle word wrap

    Example output

    cluster-logging.v6.2.4    Red Hat OpenShift Logging   6.2.4     cluster-logging.v6.2.3    Succeeded
    Copy to Clipboard Toggle word wrap

    Note the first field in the output, it indicates the currentCSV value.

  5. Delete the subscription associated with the Red Hat OpenShift Logging Operator by running the following command:

    $ oc delete subscriptions.operators.coreos.com cluster-logging -n openshift-logging
    Copy to Clipboard Toggle word wrap
  6. Delete the CSV object for Red Hat OpenShift Logging Operator in the target namespace using the currentCSV value obtained from the earlier step:

    $ oc delete csv cluster-logging.v6.2.4 -n openshift-logging
    Copy to Clipboard Toggle word wrap
  7. Uninstall the Red Hat OpenShift Logging Operator by running the following command:

    $ oc delete OperatorGroup <name> -n openshift-logging
    Copy to Clipboard Toggle word wrap

Delete the Red Hat OpenShift Logging Operator by using the Red Hat OpenShift Logging web console.

Prerequisites

  • You have administrator permissions.
  • You have access to the Red Hat OpenShift Logging web console.

Procedure

  1. In the web console, go to Operators Installed Operators.
  2. Find Red Hat OpenShift Logging Operator in the list and click kebab next to it, then click Uninstall Operator.
  3. In the pop-up select Delete all operand instances for this operator and click Uninstall.

1.2. Uninstalling the Loki Operator

You can uninstall Loki Operator by using either the OpenShift CLI (oc) or the Red Hat OpenShift Logging web console. After uninstalling Loki Operator, delete persistent volume claims (PVCs) if you do not want to reuse them in other installations of LokiStack.

1.2.1. Deleting the Loki Operator by using the CLI

Delete the Loki Operator by using the OpenShift CLI (oc).

Prerequisites

  • You have administrator permissions.
  • You installed the OpenShift CLI (oc).

Procedure

  1. Delete the LokiStack custom resource (CR) by running the following command:

    $ oc delete LokiStack logging-loki -n openshift-logging
    Copy to Clipboard Toggle word wrap

    Substitute logging-loki with the name of your LokiStack CR if you have used a different name.

  2. Check the current version of the subscribed Loki Operator in the currentCSV field by running the following command:

    $ oc get csv -n openshift-operators-redhat | grep loki-operator
    Copy to Clipboard Toggle word wrap

    Example output

    loki-operator.v6.2.4      Loki Operator               6.2.4     loki-operator.v6.2.3                    Succeeded
    Copy to Clipboard Toggle word wrap

    Note the first field in the output, it indicates the currentCSV value.

  3. Delete the subscription associated with the Loki Operator by running the following command:

    $ oc delete subscriptions.operators.coreos.com loki-operator -n openshift-operators-redhat
    Copy to Clipboard Toggle word wrap
  4. Delete the CSV object for Loki Operator in the target namespace using the currentCSV value obtained from the earlier step:

    $ oc delete csv loki-operator.v6.2.4 -n openshift-operators-redhat
    Copy to Clipboard Toggle word wrap
  5. Uninstall the Loki Operator by running the following command:

    $ oc delete OperatorGroup <name> -n openshift-operators-redhat
    Copy to Clipboard Toggle word wrap

1.2.2. Deleting the Loki Operator by using the web console

Delete the Loki Operator by using the Red Hat OpenShift Logging web console.

Prerequisites

  • You have administrator permissions.
  • You have access to the Red Hat OpenShift Logging web console.

Procedure

  1. In the web console, go to Operators Installed Operators.
  2. Find Loki Operator in the list and click kebab next to it, then click Uninstall Operator.
  3. In the pop-up, select Delete all operand instances for this operator and click Uninstall.

1.2.3. Deleting logging PVCs by using the CLI

You can delete persistent volume claims (PVCs) if you do not want to reuse them in other installations of LokiStack by using the OpenShift CLI (oc).

Prerequisites

  • You have administrator permissions.
  • You installed the OpenShift CLI (oc).

Procedure

  • Delete logging PVCs by running the following command:

    $ oc -n openshift-logging delete pvc -l app.kubernetes.io/name=lokistack
    Copy to Clipboard Toggle word wrap

1.2.4. Deleting logging PVCs by using the web console

You can delete persistent volume claims (PVCs) if you do not want to reuse them in other installations of LokiStack, by using the web console.

Prerequisites

  • You have administrator permissions.
  • You have access to the Red Hat OpenShift Logging web console.

Procedure

  1. In the web console, go to the Storage Persistent Volume Claims page.
  2. Click kebab next to each PVC, and select Delete Persistent Volume Claim.

1.3. Uninstalling the UIPlugin

You can uninstall UIPlugin by using either the OpenShift CLI (oc) or the Red Hat OpenShift Logging web console.

1.3.1. Deleting the UIPlugin by using the CLI

Delete the UIPlugin by using the OpenShift CLI (oc).

Prerequisites

  • You have administrator permissions.
  • You installed the OpenShift CLI (oc).

Procedure

  • Delete the UIPlugin by running the following command:

    $ oc delete uiplugin logging
    Copy to Clipboard Toggle word wrap

1.3.2. Deleting the UIPlugin by using the web console

Delete the UIPlugin plugin by using the Red Hat OpenShift Logging web console.

Prerequisites

  • You have administrator permissions.
  • You have access to the Red Hat OpenShift Logging web console.

Procedure

  1. In the web console, go to Operators Installed Operators.
  2. Click Cluster Observability Operator from the Installed Operators list and go to the UIPlugin tab.
  3. Click kebab for the UIPlugin logging entry and select Delete UIPlugin.
返回顶部
Red Hat logoGithubredditYoutubeTwitter

学习

尝试、购买和销售

社区

关于红帽文档

通过我们的产品和服务,以及可以信赖的内容,帮助红帽用户创新并实现他们的目标。 了解我们当前的更新.

让开源更具包容性

红帽致力于替换我们的代码、文档和 Web 属性中存在问题的语言。欲了解更多详情,请参阅红帽博客.

關於紅帽

我们提供强化的解决方案,使企业能够更轻松地跨平台和环境(从核心数据中心到网络边缘)工作。

Theme

© 2025 Red Hat