Uninstalling the External Secrets Operator for Red Hat OpenShift
You can remove the External Secrets Operator for Red Hat OpenShift from OpenShift Container Platform by uninstalling the Operator and removing its related resources.
Uninstalling the External Secrets Operator for Red Hat OpenShift using the web console
You can uninstall the External Secrets Operator for Red Hat OpenShift by using the web console.
-
You have access to the cluster with
cluster-adminprivileges. -
You have access to the OpenShift Container Platform web console.
-
The External Secrets Operator is installed.
-
Log in to the OpenShift Container Platform web console.
-
Uninstall the External Secrets Operator for Red Hat OpenShift using the following steps:
-
Navigate to Ecosystem → Installed Operators.
-
Click the Options menu
next to the External Secrets Operator for Red Hat OpenShift entry and click Uninstall Operator.
-
In the confirmation dialog, click Uninstall.
-
Removing External Secrets Operator for Red Hat OpenShift resources by using the web console
To clean up your cluster after uninstalling the External Secrets Operator for Red Hat OpenShift, remove its associated resources. This deletes residual components, such as deployments and custom resource definitions.
-
You have access to the cluster with
cluster-adminprivileges. -
You have access to the OpenShift Container Platform web console.
-
Log in to the OpenShift Container Platform web console.
-
Remove the deployments of the
external-secretsapplication components in theexternal-secretsnamespace:-
Click the Project drop-down menu to see a list of all available projects, and select the external-secrets project.
-
Navigate to Workloads → Deployments.
-
Select the deployment that you want to delete.
-
Click the Actions drop-down menu, and select Delete Deployment to see a confirmation dialog box.
-
Click Delete to delete the deployment.
-
-
Remove the custom resource definitions (CRDs) that were installed by the External Secrets Operator using the following steps:
-
Navigate to Administration → CustomResourceDefinitions.
-
Choose
external-secrets.io/component: controllerfrom the suggestions in the Label field to filter the CRDs. -
Click the Options menu
next to each of the following CRDs, and select Delete Custom Resource Definition:
-
ACRAccessToken
-
ClusterExternalSecret
-
ClusterGenerator
-
ClusterPushSecret
-
ClusterSecretStore
-
ECRAuthorizationToken
-
ExternalSecret
-
GCRAccessToken
-
GeneratorState
-
GithubAccessToken
-
Grafana
-
MFA
-
Password
-
PushSecret
-
QuayAccessToken
-
SecretStore
-
SSHKey
-
STSSessionToken
-
UUID
-
VaultDynamicSecret
-
Webhook
-
-
-
Remove the
external-secrets-operatornamespace using the following steps:-
Navigate to Administration → Namespaces.
-
Click the Options menu
next to the External Secrets Operator and select Delete Namespace.
-
In the confirmation dialog, enter
external-secrets-operatorin the field and click Delete.
-
Removing External Secrets Operator for Red Hat OpenShift resources by using the CLI
After you have uninstalled the External Secrets Operator for Red Hat OpenShift, you can optionally eliminate its associated resources from your cluster by using the command-line interface (CLI).
-
You have access to the cluster with
cluster-adminprivileges.
-
Delete the deployments of the
external-secretsapplication components in theexternal-secretsnamespace by running the following command:$ oc delete deployment -n external-secrets -l app=external-secrets -
Delete the custom resource definitions (CRDs) that were installed by the External Secrets Operator by running the following command:
$ oc delete customresourcedefinitions.apiextensions.k8s.io -l external-secrets.io/component=controller -
Delete the
external-secrets-operatornamespace by running the following command:$ oc delete project external-secrets-operator