The sample application busybox can be deleted by using the Red Hat
Advanced Cluster Management for Kubernetes (RHACM) console.
Before you begin
Important: When deleting a DR protected application, access to both clusters that belong
to the DRPolicy is required. This is to ensure that all protected API resources and resources in the
respective S3 stores are cleaned up as part of removing the DR protection. If access to one of the
clusters is not healthy, deleting the DRPlacementControl resource for the
application, on the hub, would remain in the Deleting state.
Do not begin deleting a sample application until the failover and relocate testing is completed
and the application is ready to be removed from RHACM and the managed clusters.
Procedure
- On the Hub cluster, navigate to Applications.
- Search for the sample application to be deleted (for example,
busybox).
- Click the Action menu next to the application that you want to
delete.
- Click Delete application.
When the Delete application is selected a new screen appears asking if the
application-related resources should also be deleted.
- Select Remove application related resources to delete the
Subscription and PlacementRule.
- Click Delete.
This deletes the
busybox application on the Primary-managed cluster (or the cluster that the
application was running on).
- In addition to the resources deleted by using the RHACM console, delete the
DRPlacementControl if it is not auto-deleted after deleting the
busybox application.
- Log in to the Red Hat OpenShift web console for the Hub cluster and navigate to
Installed Operators for the project
busybox-sample. For ApplicationSet applications, select the project as
openshift-gitops.
- Click .
- Click the Action menu next to the
busybox
application DRPlacementControl that you want to delete.
- Click Delete DRPlacementControl.
- Click Delete.
Note: This process can be used to delete any application with a DRPlacementControl
resource.