A Key Information About OSO

This section provides important information that the user must know about OSO.

The following are some of the important points about OSO installation that you must be aware of:

1. All the services having GUI are converted to ClusterIP as Cloud Native Configuration Console (CNC Console) hyperlinks for OSO GUIs are currently not enabled. Therefore, you can access the GUIs through CNC Console only.
   Run the following command to get the list of services and check their service type.

   $ kubectl get service -n <namespace>

   Sample output:

   
   NAME                             TYPE          CLUSTER-IP      EXTERNAL-IP   	 PORT(S)         AGE
   oso-prom-alm                   ClusterIP       10.233.48.28       <none>        80:31717/TCP        4d13h
   oso-prom-alm-headless          ClusterIP       None               <none>        80/TCP,6783/TCP     4d13h
   oso-prom-svr                   ClusterIP       10.233.22.117      <none>        80:30266/TCP        4d13h

2. Since Alertmanager is a StatefulSets, the Persistent Volume (PV) or Persistent Volume Claim (PVC) do not get deleted automatically when the following helm uninstallation command is run for the respective OSO helm-release:

   $ helm3 uninstall oso-release-name -n <namespace>

   This uninstallation command removes all resources related to the OSO release. However it does not remove the PVs or PVCs for Alertmanager. Therefore, perform the following steps to manually remove PVs and PVCs in Alertmanager:
   1. Run the following command to retrieve the list of PVCs:

      $ kubectl get pvc -n <namespace>

      Sample output:

      
      NAME             STATUS    VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS   AGE
      oso-prom-svr     BOUND     pvc-a639c8cb-eee1-4fa3-be1b-d4c4e5d66b9a   8Gi        RWO            standard       159m
      oso-prom-alm-0   BOUND     pvc-a639c8cb-eee1-4fa3-be1b-d4c4e5d6689J   2Gi        RWO            standard       159m
      oso-prom-alm-1   BOUND     pvc-a639c8cb-eee1-4fa3-be1b-d4c4e5d6689k   2Gi        RWO            standard       159m

   2. Run the following command to delete the PVCs:

      $ kubectl delete pvc oso-prom-svr oso-prom-alm-0 oso-prom-alm-1 -n <namespace>

      Sample output:

      
      persistentvolumeclaim "oso-prom-svr" deleted
      persistentvolumeclaim "oso-prom-alm-0" deleted
      persistentvolumeclaim "oso-prom-alm-1" deleted

   3. Run the following command to retrieve the PV details:

      $ kubectl get pv -n <namespace>

      Sample output:

      
      NAME                                      CAPACITY  ACCESS MODES    RECLAIM POLICY   STATUS    CLAIM                                                       STORAGECLASS       REASON   AGE
      pvc-104a1c0c-72f7-4ae0-b368-71c4e22082ce   2Gi        RWO            Delete           Bound    osoxyz2/storage-volume-oso-xyz2-prom-alm-1           standard                   4d13h
      pvc-1e75d93e-0731-45f2-9ef7-46cf8cbbb3f9   2Gi        RWO            Delete           Bound    osoxyz1/storage-volume-oso-xyz-prom-alm-0            standard                   4d13h
      pvc-30400fe7-61dd-4e2f-8a50-149e4e14be90   2Gi        RWO            Delete           Bound    osoxyz2/oso-xyz2-prom-svr                            standard                   4d12h

   4. Run the following command to delete the PVs:

      $ kubectl delete pv pvc-104a1c0c-72f7-4ae0-b368-71c4e22082ce pvc-1e75d93e-0731-45f2-9ef7-46cf8cbbb3f9 pvc-30400fe7-61dd-4e2f-8a50-149e4e14be90 -n osoxyz1

3. Alertmanager has persistent storage enabled in this release to store notifications and silences.