Chapter 7. Uninstalling an Operator installation on OpenShift Container Platform
To delete the dynamic plug-ins from your installation, you must edit the ConfigMaps that reference Ansible.
The deployment auto reloads when the ConfigMaps are updated. You do not need to reload the deployment manually.
7.1. Removing the Ansible plug-ins from the ConfigMap Copy linkLink copied to clipboard!
To remove the Ansible plug-ins from an Operator installation, you must edit the custom ConfigMap that references the plug-ins. You can either delete the entire plug-in entry block or simply disable the plug-ins by setting the disabled attribute to true.
Procedure
Open the custom ConfigMap where you referenced the Ansible plug-ins.
For this example, the ConfigMap name is
rhaap-dynamic-plugins-config.Locate the dynamic plug-ins in the
plugins:block.For OCI delivery, the entries to remove or disable:
plugins: - disabled: false package: 'oci://registry.redhat.io/ansible-automation-platform/automation-portal:2.1!ansible-plugin-backstage-rhaap' pluginConfig: ... - disabled: false package: 'oci://registry.redhat.io/ansible-automation-platform/automation-portal:2.1!ansible-plugin-scaffolder-backend-module-backstage-rhaap' pluginConfig: ...-
For HTTP plug-in registry, the entries use
http://plugin-registry:8080/...URLs instead.
- Click .
7.2. Removing Ansible Automation Platform and Dev Spaces from the custom Red Hat Developer Hub ConfigMap Copy linkLink copied to clipboard!
To remove Ansible Automation Platform and Dev Spaces configuration from an Operator installation, you must edit the custom Red Hat Developer Hub ConfigMap.
Procedure
Open the custom Red Hat Developer Hub ConfigMap where you added configuration for the templates and for connecting to Ansible Automation Platform and Dev Spaces. In this example, the Red Hat Developer Hub ConfigMap name is
app-config-rhdh.kind: ConfigMap apiVersion: v1 metadata: name: rhdh-app-config data: app-config-custom.yaml: | ... catalog: ... locations: # Remove the YAML entry below the 'locations' YAML key - type: url target: https://github.com/ansible/ansible-rhdh-templates/blob/main/all.yaml rules: - allow: [Template] ... # Remove the entire 'ansible' YAML key and all sub-entries ansible: devSpaces: baseUrl: '<https://YOUR_DEV_SPACES_URL>' creatorService: baseUrl: '127.0.0.1' port: '8000' rhaap: baseUrl: '<https://YOUR_AAP_URL>' token: <REDACTED> checkSSL: false-
Remove the
urlin thelocations:block to delete the templates from the RHDH instance. -
Remove the
ansible:block to delete the Ansible-specific configuration. - Click .
7.3. Uninstalling the sidecar container Copy linkLink copied to clipboard!
To remove the sidecar container for Ansible development tools from the developer-hub pod, you must modify the base ConfigMap for the Red Hat Developer Hub deployment.
Procedure
- In the OpenShift console, select the Topology view.
- Click More actions ⋮ on the developer-hub instance and select Edit backstage to edit the base ConfigMap.
- Select the YAML tab.
In the editing pane, remove the
containersblock for the sidecar container from thespec.deployment.patch.spec.template.specblock:... spec: deployment: patch: spec: template: spec: containers: - command: - adt - server image: registry.redhat.io/ansible-automation-platform-25/ansible-dev-tools-rhel8:latest imagePullPolicy: always ports: - containerPort: 8000 protocol: TCP terminationMessagePolicy: file- Click .
If you used OCI delivery, delete the registry auth secret:
oc delete secret <deployment-name>-dynamic-plugins-registry-authIf you used the HTTP plug-in registry, remove the plug-in registry application:
oc delete all -l app=plugin-registry