7 Uninstalling OSO

This chapter provides information about uninstalling Oracle Communications Cloud Native Core, Operations Services Overlay (OSO).

7.1 Uninstalling OSO Using Helm

To uninstall OSO, run the following commands:

  1. [Optional]: Take backup of prometheus data using Creating Backup of Prometheus Time Series Database (TSDB) Using Snapshot Utility.
  2. Run the following command to list all the OSO components installed using OSO namespace.
    $ helm list -n <oso-namespace>

    For example: $ helm list -n oso

    Sample output:
    
    NAME            NAMESPACE       REVISION        UPDATED                                 STATUS          CHART                   APP VERSION
    oso-alm         oso             1               2026-01-22 07:21:12.915700279 +0000 UTC deployed        alertmanager-1.15.1     25.2.200
    oso-alrt-config oso             1               2026-01-22 11:57:34.950494069 +0000 UTC deployed        oso-alr-config-0.1.0    25.2.200
    oso-apm         oso             1               2026-01-22 07:21:14.085348726 +0000 UTC deployed        apm-service-25.2.200    25.2.200
    oso-prom        oso             1               2026-01-22 07:21:11.719282076 +0000 UTC deployed        prometheus-27.5.0       25.2.200
  3. Run the following command to list all the Kubernetes services:
    $ kubectl get all -n <oso-namespace>

    For example:$ kubectl get all -n oso

    Sample output:
    
    NAME                                READY   STATUS    RESTARTS   AGE
    pod/apm-svc-6584494467-zfdwv        1/1     Running   0          4h45m
    pod/oso-alm-0                       2/2     Running   0          4h42m
    pod/oso-alm-1                       2/2     Running   0          4h42m
    pod/oso-prom-svr-74cff66546-nrrd4   2/2     Running   0          4h45m
    
    NAME                       TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)                    AGE
    service/apm-svc            ClusterIP   10.233.31.59    <none>        80/TCP                     4h45m
    service/oso-alm            NodePort    10.233.11.166   <none>        80:30939/TCP               4h45m
    service/oso-alm-headless   ClusterIP   None            <none>        80/TCP,9094/TCP,9094/UDP   4h45m
    service/oso-prom-svr       NodePort    10.233.56.164   <none>        80:31048/TCP               4h45m
    
    NAME                           READY   UP-TO-DATE   AVAILABLE   AGE
    deployment.apps/apm-svc        1/1     1            1           4h45m
    deployment.apps/oso-prom-svr   1/1     1            1           4h45m
    
    NAME                                      DESIRED   CURRENT   READY   AGE
    replicaset.apps/apm-svc-6584494467        1         1         1       4h45m
    replicaset.apps/oso-prom-svr-74cff66546   1         1         1       4h45m
    
    NAME                       READY   AGE
    statefulset.apps/oso-alm   2/2     4h45m
  4. Run the following command to delete all PVCs in the OSO namespace.
    
    # Delete all pvcs
    $ kubectl delete pvc --all -n <oso-namespace> 
    

    Sample output

    
    persistentvolumeclaim "storage-oso-alm-0" deleted
    persistentvolumeclaim "storage-oso-alm-1" deleted
  5. Run the following commands to uninstall the OSO components:
    • Run the following command to uninstall oso-prometheus.
      $ helm uninstall oso-prom -n <oso-namespace>
      For example:
      $ helm uninstall oso-prom -n oso
      

      Sample output:

      release "oso-prom" uninstalled
    • Run the following command to uninstall oso-alert-manager.
      $ helm uninstall oso-alm -n <oso-namespace>
      For example:
      $ helm uninstall oso-alm -n oso
      

      Sample output:

      release "oso-alm" uninstalled
    • Run the following command to uninstall oso-apm service.
      $ helm uninstall oso-apm -n <oso-namespace>
      For example:
      $ helm uninstall oso-apm -n oso
      

      Sample output:

      release "oso-apm" uninstalled
    • Run the following command to uninstall oso-alert-config.
      $ helm uninstall oso-alrt-config -n <oso-namespace>
      For example:
      $ helm uninstall oso-alrt-config -n oso
      

      Sample output:

      release "oso-alrt-config" uninstalled
Helm keeps a record of its releases, so you can still reactivate the release after uninstalling it. Run the following command to verify if all the OSO related resources are uninstalled.
$ kubectl get all -n <oso-namespace>
Sample output:

NAME                               COMPLETIONS   DURATION   AGE
oso-alr-config-hook-post-install   0/1           138m       138m

In case of successful uninstallation, no OSO resource is displayed in the command output.

If the command output displays the OSO resources or objects, then perform Deleting Kubernetes Resources.

7.2 Deleting Kubernetes Resources

This section describes how to delete Kubernetes resources or objects where OSO is deployed.

Caution:

Be sure before running the following command as it deletes all the Kubernetes objects in the specified namespace.

Run the following command to delete the Kubernetes specific resources:

kubectl delete <resource-type> <resource-name> -n <release-namespace>

For example:

$ kubectl delete job oso-alr-config-hook-post-install
Sample output:
job.batch "oso-alr-config-hook-post-install" deleted