mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
97bae04edb
resolving error in HCP topic map indentation removed the < and replaced with brackets for tech preview in HCP topic map removed the < and replaced with brackets for Operators tech preview in HCP topic map removed the file with tech preview for Operators in HCP topic map applied conditions to 20 xrefs because the networking, cli, authentication and observability books are not in HCP repo yet added blank line after and endif and an include module
23 lines
1.3 KiB
Plaintext
23 lines
1.3 KiB
Plaintext
:_mod-docs-content-type: ASSEMBLY
|
|
[id="olm-deleting-operators-from-a-cluster"]
|
|
= Deleting Operators from a cluster
|
|
include::_attributes/common-attributes.adoc[]
|
|
:context: olm-deleting-operators-from-a-cluster
|
|
|
|
toc::[]
|
|
|
|
The following describes how to delete, or uninstall, Operators that were previously installed using Operator Lifecycle Manager (OLM) on your {product-title} cluster.
|
|
|
|
[IMPORTANT]
|
|
====
|
|
You must successfully and completely uninstall an Operator prior to attempting to reinstall the same Operator. Failure to fully uninstall the Operator properly can leave resources, such as a project or namespace, stuck in a "Terminating" state and cause "error resolving resource" messages to be observed when trying to reinstall the Operator.
|
|
|
|
ifndef::openshift-dedicated,openshift-rosa,openshift-rosa-hcp[]
|
|
For more information, see xref:../../operators/admin/olm-troubleshooting-operator-issues.adoc#olm-reinstall_olm-troubleshooting-operator-issues[Reinstalling Operators after failed uninstallation].
|
|
endif::openshift-dedicated,openshift-rosa,openshift-rosa-hcp[]
|
|
====
|
|
|
|
include::modules/olm-deleting-operators-from-a-cluster-using-web-console.adoc[leveloffset=+1]
|
|
include::modules/olm-deleting-operators-from-a-cluster-using-cli.adoc[leveloffset=+1]
|
|
include::modules/olm-refresh-subs.adoc[leveloffset=+1]
|