Red Hat Summit Red Hat Summitサポートコンソール開発者トライアルの開始お問い合わせ

1.7. Deleting old resources

1.7.1. Deleting the ClusterLogging instance
リンクのコピー

Delete the ClusterLogging instance because it is no longer needed in Logging 6.x.

Prerequisites

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

Procedure

  • Delete the ClusterLogging instance. 

    $ oc delete clusterlogging <CR name> -n <namespace>

Verification

  1. Verify that no collector pods are running by running the following command: 

    $ oc get pods -l component=collector -n <namespace>

  2. Verify that no clusterLogForwarder.logging.openshift.io custom resource (CR) exists by running the following command: 

    $ oc get clusterlogforwarders.logging.openshift.io -A
重要

If any clusterLogForwarder.logging.openshift.io CR is listed, it belongs to the old 5.x Logging stack, and must be removed. Create a backup of the CRs and delete them before deploying any clusterLogForwarder.observability.openshift.io CR with the new APIversion.

1.7.2. Deleting Red Hat OpenShift Logging 5 CRD
リンクのコピー

Delete Red Hat OpenShift Logging 5 custom resource definitions (CRD) when upgrading to Logging 6.

Prerequisites

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

Procedure

  • Delete clusterlogforwarders.logging.openshift.io and clusterloggings.logging.openshift.io CRD by running the following command: 

    $ oc delete crd clusterloggings.logging.openshift.io clusterlogforwarders.logging.openshift.io

1.7.3. Uninstalling Elasticsearch
リンクのコピー

You can uninstall Elasticsearch by using the OpenShift Container Platform web console. Uninstall Elasticsearch only if it is not used for by component such as Jaeger, Service Mesh, or Kiali.

Prerequisites

  • You have administrator permissions.
  • If you have not already removed the Red Hat OpenShift Logging Operator and related resources, you must remove references to Elasticsearch from the ClusterLogging custom resource.

Procedure

  1. Go to the Administration Custom Resource Definitions page, and click Elasticsearch.
  2. On the Custom Resource Definition Details page, click Instances.
  3. Click the Options menu kebab next to the instance, and then click Delete Elasticsearch.
  4. Go to the Administration Custom Resource Definitions page.
  5. Click the Options menu kebab next to Elasticsearch, and select Delete Custom Resource Definition.
  6. Go to the Operators Installed Operators page.
  7. Click the Options menu kebab next to the OpenShift Elasticsearch Operator, and then click Uninstall Operator.

  8. Optional: Delete the openshift-operators-redhat project.

    重要

    Do not delete the openshift-operators-redhat project if other global Operators are installed in this namespace.

    1. Go to the Home Projects page.
    2. Click the Options menu kebab next to the openshift-operators-redhat project, and then click Delete Project.
    3. Confirm the deletion by typing openshift-operators-redhat in the dialog box, and then click Delete.
Red Hat logoGithubredditYoutubeTwitter

詳細情報

試用、購入および販売

コミュニティー

会社概要

Red Hat は、企業がコアとなるデータセンターからネットワークエッジに至るまで、各種プラットフォームや環境全体で作業を簡素化できるように、強化されたソリューションを提供しています。

多様性を受け入れるオープンソースの強化

Red Hat では、コード、ドキュメント、Web プロパティーにおける配慮に欠ける用語の置き換えに取り組んでいます。このような変更は、段階的に実施される予定です。詳細情報: Red Hat ブログ.

Red Hat ドキュメントについて

Red Hat をお使いのお客様が、信頼できるコンテンツが含まれている製品やサービスを活用することで、イノベーションを行い、目標を達成できるようにします。 最新の更新を見る.

Legal Notice

Theme

© 2026 Red Hatトップに戻る