Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Add_workflow_for_techpubs
AUTH2UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cb8305e9, userName='null'}
AUTH1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cd5909df, userName='null'}
JIRAIDAUTHSBX-0000
REV5UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c90501da, userName='null'}
REV6UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cdcd0ab1, userName='null'}
REV3UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cbba0643, userName='null'}
REV1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cc2c0791, userName='null'}



Internal_display_only


Available_since
TypeAvailable Since
Release12.1.1


Panel

In this section:

Table of Contents
maxLevel4
minLevel2


Uninstalling SBC CNe using Helm

  1. List the Helm charts that are deployed in the cluster.

    Code Block
    languagetext
    [jdoe@cli-blr-1 12.1.1-142_build_SBC]$ helm list
    NAME           NAMESPACE    REVISION    UPDATED                                   STATUS        CHART                      APP VERSION 
    vgsbc          sbc-svt      3           2024-03-05 20:35:40.949699595 +0530 IST   deployed      rbbn-core-cnf-12.1.1-135   12.1.1-135


  2. Uninstall the SBC CNe deployment.

    Code Block
    #helm uninstall mysiprec


Once the Helm uninstall command completes, verify that all of the resources (for example, Deployment, Statefulset, Replicaset, Pods, Configmap, Role/RoleBindings, PVCs, Jobs, and so on) are deleted under the namespace where the SBC CNe is deployed.

Info
titleNote

To ensure that associated PVCs are getting deleted automatically during the Helm uninstall, set deleteCachePvc to "true" in the Helm chart at the time of instantiation. Since the redis-cache pod is statefulset, when the helm uninstall command is performed, the PVCs associated to the redis-cache pods/statefulset won't be deleted if deleteCachePvc is set to "false" . In that case, manually delete the PVCs using:

#oc delete pvc <redis-cache-pvc-names>

Uninstalling SBC CNe using Git

  1. Edit the kustomization.yaml file to remove the SBC CNe deployment file name initially added during the installation of the SBC CNe via git.

    Code Block
    languagetext
    apiVersion: kustomize.config.k8s.io/v1beta1
    kind: Kustomization
    nameSuffix: -jdoe
    resources:
       - values_sbc.yaml   ---> This is the name of the HelmRelease file


  2. Commit and Push the changes using Git commands.  After the reconciliation via FluxCD, the SBC CNe deployment will be uninstalled from the cluster.
  3. Make sure all the resources (for example: Deployment, Statefulset, Replicaset, Pods, Configmap, Role/RoleBindings, PVCs, Jobs, and so on) under the namespace (where the SBC CNe is deployed) are deleted.


Info
titleNote

To ensure that associated PVCs are getting deleted automatically during the Helm uninstall, set deleteCachePvc to "true" in the Helm chart at the time of instantiation. Since the redis-cache pod is statefulset, when the helm uninstall command is performed, the PVCs associated to the redis-cache pods/statefulset won't be deleted if deleteCachePvc is set to "false" . In that case, manually delete the PVCs using:

#oc delete pvc <redis-cache-pvc-names>