Red Hat Summit Red Hat SummitSupportConsoleDéveloppeursCommencer un essaiContact

Ce contenu n'est pas disponible dans la langue sélectionnée.

Chapter 1. Uninstalling logging

1.1. Uninstalling the Red Hat OpenShift Logging Operator
Copier lien

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

    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
     
    $ oc adm policy remove-cluster-role-from-user collect-application-logs -z logging-collector -n openshift-logging
     
    $ oc adm policy remove-cluster-role-from-user collect-infrastructure-logs -z logging-collector -n openshift-logging
     
    $ oc adm policy remove-cluster-role-from-user collect-audit-logs -z logging-collector -n openshift-logging
     
    $ oc adm policy remove-cluster-role-from-user logging-collector-logs-writer -z logging-collector -n openshift-logging
     
    $ oc delete serviceaccount logging-collector -n openshift-logging

  3. Delete the LogFileMetricExporter resource if you have deployed it by running the following command: 

    $  oc -n openshift-logging delete LogFileMetricExporter --all

  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

    Example output

    cluster-logging.v6.2.4    Red Hat OpenShift Logging   6.2.4     cluster-logging.v6.2.3    Succeeded

    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

  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

  7. Uninstall the Red Hat OpenShift Logging Operator by running the following command: 

    $ oc delete OperatorGroup <name> -n openshift-logging

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
Copier lien

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
Copier lien

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

    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

    Example output

    loki-operator.v6.2.4      Loki Operator               6.2.4     loki-operator.v6.2.3                    Succeeded

    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

  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

  5. Uninstall the Loki Operator by running the following command: 

    $ oc delete OperatorGroup <name> -n openshift-operators-redhat

1.2.2. Deleting the Loki Operator by using the web console
Copier lien

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
Copier lien

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

Next steps

1.2.4. Deleting logging PVCs by using the web console
Copier lien

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.

Next steps

1.3. Uninstalling the UIPlugin
Copier lien

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
Copier lien

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

1.3.2. Deleting the UIPlugin by using the web console
Copier lien

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

Apprendre

Essayez, achetez et vendez

Communautés

À propos de Red Hat

Nous proposons des solutions renforcées qui facilitent le travail des entreprises sur plusieurs plates-formes et environnements, du centre de données central à la périphérie du réseau.

Rendre l’open source plus inclusif

Red Hat s'engage à remplacer le langage problématique dans notre code, notre documentation et nos propriétés Web. Pour plus de détails, consultez le Blog Red Hat.

À propos de la documentation Red Hat

Nous aidons les utilisateurs de Red Hat à innover et à atteindre leurs objectifs grâce à nos produits et services avec un contenu auquel ils peuvent faire confiance. Découvrez nos récentes mises à jour.

Legal Notice

Theme

© 2026 Red HatRetour au début