1
0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Files
openshift-docs/modules/external-secrets-operator-delete-upstream-operatorconfig.adoc
2025-11-26 19:43:48 +00:00

66 lines
1.7 KiB
Plaintext

// Module included in the following assemblies:
//
// * security/external_secrets_operator/external-secrets-operator-migrate-downstream-upstream.adoc
:_mod-docs-content-type: PROCEDURE
[id="external-secrets-operator-delete-upstream-operatorconfig_{context}"]
= Deleting the community {external-secrets-operator-short}
[role="_abstract"]
Delete the configuration resource for the community Operator so that the legacy application is fully removed. This action prevents conflicts before installing the {external-secrets-operator}.
.Prerequisites
* You must be logged in as a user with the `cluster-admin` role.
* You must have the `oc` command-line tool installed and configured.
.Procedure
. Find your community Operator's `namespace` by running the following command:
+
[source,terminal]
----
$ oc get operatorconfigs.operator.external-secrets.io -A
----
+
The following is an example of finding the `namespace`:
+
[source,terminal]
----
NAMESPACE NAME AGE
external-secrets cluster 9m18s
----
. Delete the `operatorconfig` by running the following command:
+
[source,terminal]
----
$ oc delete operatorconfig <config_name> -n <operator_namespace>
----
.Verification
. To verify that the `operatorconfig` is deleted, run the following command:
+
[source,terminal]
----
$ oc get operatorconfig -n <operator_namespace>
----
+
The command must return `no resource found`.
. To verify that the old webhooks are deleted, run the following commands:
+
[source,terminal]
----
$ oc get validatingwebhookconfigurations | grep external-secrets
----
+
[source,terminal]
----
$ oc get mutatingwebhookconfigurations | grep external-secrets
----
+
The commands must return no results.