Removing External Secrets Operator for Red Hat OpenShift resources by using the web console
After you have uninstalled the External Secrets Operator for Red Hat OpenShift, you can optionally eliminate its associated resources from your cluster.
-
You have access to the cluster with
cluster-adminprivileges. -
You have access to the Red Hat OpenShift Container Platform web console.
-
Log in to the Red Hat 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.
-