# Transform-the-suite-to-a-Helm-deployment-on-24.3.2_688996421
#### Helm upgrade procedure

<table><colgroup><col> <col> <col> <col> <col> <col></colgroup><tbody><tr><th></th><th>SEQ</th><th>Steps</th><th>Duration</th><th>Downtime</th><th></th></tr><tr><td rowspan="2"><h3>Prerequisites</h3></td><td>1</td><td><p>Make sure current suite is upgraded to version 24.3.2</p></td><td>1 min</td><td rowspan="2">NA</td><td></td></tr><tr><td>2</td><td><p>Run the following command to make sure that all the OMT and suite pods are ready</p></td><td>1 min</td><td><pre><code>kubectl get pod --all-namespaces|grep -v 1/1|grep -v 2/2|grep -v 3/3|grep -v 4/4|grep -v Completed</code></pre></td></tr><tr><td rowspan="9"><h3>Preparation</h3></td><td>1</td><td><p>Download the ESM helm chart to bastion</p></td><td>2 mins</td><td rowspan="9">NA</td><td><p>Download & Unzip & Verify the signature</p></td></tr><tr><td>2</td><td>Get environment variables</td><td>1 min</td><td><p>Run below commands to get ENV variables:</p><p>NAMESPACE=`kubectl get namespace|grep itsma | cut -f1 -d " "`<br>SYSTEM_USER_ID=$(kubectl get configmap -o jsonpath='{.data.system_user_id}' itsma-common-configmap -n $NAMESPACE)<br>SYSTEM_GROUP_ID=$(kubectl get configmap -o jsonpath='{.data.system_group_id}' itsma-common-configmap -n $NAMESPACE)<br>SIZE=$(kubectl get configmap -o jsonpath='{.data.itom_suite_size}' itsma-common-configmap -n $NAMESPACE)<br>echo NAMESPACE: $NAMESPACE SYSTEM_USER_ID: ${SYSTEM_USER_ID}, SYSTEM_GROUP_ID: ${SYSTEM_GROUP_ID}, SIZE: ${SIZE}</p><p>NOTE: If your bastion session is expired, run this get ENV variables again. If it expires after you delete the ns, replace the variables manually when executing the command</p></td></tr><tr><td>3</td><td>Backup the <strong>suite external ingress</strong> and <strong>suite integration ingress</strong>.</td><td></td><td><p><strong>If you don't have Backup the ingress yaml files which will be used in helm install step to the tmp folder:</strong></p><p><strong>NOTE: The ingress names may differ between farms.</strong></p><p>kubectl get ingress sma-ingress -n $NAMESPACE -o yaml > suite-ingress-backup.yaml</p><p>kubectl get ingress sma-int-ingress -n $NAMESPACE -o yaml > sma-int-ingress-backup.yaml</p></td></tr><tr><td>4</td><td><p>Create additional volumes</p><p>Configure NFS volume</p></td><td>1 min</td><td><p>For EKS:</p><p>Run the following commands on the bastion node.</p><p><strong>NOTE: Please change the mount point with the actual value:</strong></p><p>sudo mkdir -p /mnt/efs/var/vols/itom/itsma/config-volume<br>sudo mkdir -p /mnt/efs/var/vols/itom/itsma/logging-volume<br>sudo chown -R $SYSTEM_USER_ID:$SYSTEM_GROUP_ID /mnt/efs/var/vols/itom/itsma/config-volume<br>sudo chown -R $SYSTEM_USER_ID:$SYSTEM_GROUP_ID /mnt/efs/var/vols/itom/itsma/logging-volume<br>sudo chmod g+w /mnt/efs/var/vols/itom/itsma/config-volume<br>sudo chmod g+w /mnt/efs/var/vols/itom/itsma/logging-volume<br>sudo chmod g+s /mnt/efs/var/vols/itom/itsma/config-volume<br>sudo chmod g+s /mnt/efs/var/vols/itom/itsma/logging-volume</p></td></tr><tr><td>5</td><td><p>Check folder permissions</p></td><td>10 mins</td><td><p><strong>Using the following command to check and change folder permission (Please replace the mount point with actual value:):</strong></p><p>Check folder permission:</p><p>sudo find /mnt/efs/var/vols/itom -type d -exec stat --format='%u:%g %A %n' '{}' \;| grep -v $SYSTEM_USER_ID:$SYSTEM_GROUP_ID</p><p>If the result doesn't include <code><SYSTEM_USER_ID>:<SYSTEM_GROUP_ID></code>, change the ownership of each directory or file that you created by using the <strong><code>chown -R <SYSTEM_USER_ID>:<SYSTEM_GROUP_ID> <MOUNT_POINT></code></strong> command.</p><p>For example (the command find and update the folders' permission exclude the log folder):</p><p>sudo find /mnt/efs/var/vols/itom -type d -not -path "/mnt/efs/var/vols/itom/itsma/global-volume/logs/*" -exec chown $SYSTEM_USER_ID:$SYSTEM_GROUP_ID {} +</p></td></tr><tr><td>6</td><td><p>Sync data to new Helm persistent volumes</p></td><td>35 mins</td><td><p><strong>NOTE: Please use the syncData.sh script which in 24.4 GA release package.</strong></p><p>NOTE: You may want to clean up the tenant-import and tenant-export folders before sync.</p><p>cd ESM_Helm_Chart-2x.x/scripts/transformation<br>chmod u+x syncData.sh</p><p><strong>Use the following command to avoid bastion connection interruption during sync data (Please replace the mount point to actual value you use):</strong></p><p>nohup sh -c "printf 'y\ny\ny\ny\n' | sudo./syncData.sh --globalVolumePath /mnt/efs/var/vols/itom/itsma/global-volume --smartanalyticsVolumePath /mnt/efs/var/vols/itom/itsma/smartanalytics-volume --configVolumePath /mnt/efs/var/vols/itom/itsma/config-volume" </dev/null >nohup.out 2>&1 &</p><p><strong>Watch the progress by below command:</strong></p><p>tail -f nohup.out</p><p>For the information, 35 mins for below data size:</p><p>The 'global-volume' requires an additional 33 G of free disk space.<br>The 'config-volume' requires an additional 1.5 G of free disk space.</p></td></tr><tr><td rowspan="2">7</td><td rowspan="2"><p>Retrieve system configurations and generate values.yaml file</p><ul><li>Generate basic values.yaml</li><li><p>Generate customized values.yaml</p></li></ul></td><td rowspan="2">5 mins</td><td><p>Before you begin, ensure that the <strong>jq and yq</strong> tools are installed</p><p><strong>Create a values.yaml file based on the suite environment</strong></p><p>cd ESM_Helm_Chart-2x.x/scripts/transformation<br>chmod u+x generateBasicValuesYaml.sh<br>./generateBasicValuesYaml.sh</p><p>Copy the <code>values.yaml</code> file to the ESM_Helm_Chart-2x.x/charts/ directory.</p><p>Save a copy of the <code>values.yaml</code> file in a secure location as backup.</p></td></tr><tr><td><p><strong>Generate customized values.yaml</strong></p><p>Go to the <code>ESM_Helm_Chart-2x.x/scripts/custom_settings</code> directory.Change the script file permission and run script:</p><p>cd ESM_Helm_Chart-2x.x/esm-1.0.0+2x.x-xxx/scripts/ <strong>custom_settings</strong></p><p>chmod u+x generateCustomSettings.sh</p><p>./generateCustomSettings.sh</p><p>The script generates a <code>customized_values.yaml</code> file in the current directory.</p><p>Copy the <code>customized_values.yaml</code> file to the ESM_Helm_Chart-2x.x/charts/ directory.</p><p>Copy the <code>customized_values.yaml</code> file to a secure location as a backup copy.</p></td></tr><tr><td>8</td><td><p>Back up OMT and SMA</p></td><td>30 mins</td><td><p>Backup the whole SMAX (RDS/EFS/K8S)</p></td></tr><tr><td rowspan="12"><h3>Maintain Window</h3></td><td>1</td><td><p>Stop SMA and OMT</p></td><td>10 mins</td><td rowspan="12">70 mins</td><td><p><strong>1.Stop OMT & SMA:</strong></p><p>$CDF_HOME/bin/cdfctl runlevel set -l DOWN -n $NAMESPACE<br>$CDF_HOME/bin/cdfctl runlevel set -l DOWN -n core</p><p><strong>2.Check the pods of OMT & SMA are all stopped.</strong></p><p>kubectl get pod -n $NAMESPACE|grep -v -E 'throttling|opentelemetry|toolkit|Completed'<br>kubectl get pod -n core |grep -v Completed</p><p>NOTE: In SaaS simulation ENV, promethues pods are under core namespace and it takes time to shut down these pods</p></td></tr><tr><td>2</td><td><p>Clean up classic SMA resources</p></td><td>5 mins</td><td><p><strong>Use the below command to clean the SMA resource:</strong></p><p>kubectl delete ns $NAMESPACE</p><p><strong>Verify the ns is deleted:</strong></p><p>kubectl get ns</p><p><strong>Use the following command to check what resources are being used:</strong></p><p>kubectl api-resources --verbs=list --namespaced -o name | xargs -n 1 kubectl get --show-kind --ignore-not-found -n $NAMESPACE</p><p><strong>Patch the ingress use the following command:</strong></p><p>kubectl patch ing sma-ingress -n $NAMESPACE --type=json --patch='[{"op": "remove", "path": "/metadata/finalizers/0"}]'</p></td></tr><tr><td>3</td><td><p>Sync incremental data</p></td><td>2 mins</td><td><p><strong>NOTE: Please use the syncData.sh script which in 24.4 GA release package.</strong></p><p><strong>Sync incremental data:</strong></p><p>Go to the <code>ESM_Helm_Chart-2x.x/scripts/transformation</code> directory and run below command again:</p><p>sudo./syncData.sh --globalVolumePath /mnt/efs/var/vols/itom/itsma/global-volume --smartanalyticsVolumePath /mnt/efs/var/vols/itom/itsma/smartanalytics-volume --configVolumePath /mnt/efs/var/vols/itom/itsma/config-volume</p><p>NOTE: The incremental sync should not cost long time as the first sync, while still you can use the below command to avoid bastion connection interruption during sync data(Please change the mount point as your actual environment):</p><p>nohup sh -c "printf 'y\ny\ny\ny\n' | sudo./syncData.sh --globalVolumePath /mnt/efs/var/vols/itom/itsma/global-volume --smartanalyticsVolumePath /mnt/efs/var/vols/itom/itsma/smartanalytics-volume --configVolumePath /mnt/efs/var/vols/itom/itsma/config-volume" </dev/null >nohup.out 2>&1 &</p><p><strong>Then watch the progress by below command:</strong></p><p>tail -f nohup.out</p></td></tr><tr><td>4</td><td><p>Update the label for the core ns</p></td><td>1 min</td><td><p><strong>Update the label for core:</strong></p><p>kubectl patch ns core -p '{"metadata":{"labels":{" <a>deployments.microfocus.com/deployment-name":"cdf</a> "}}}'</p></td></tr><tr><td>5</td><td><p>Create a deployment for the suite</p></td><td>1 min</td><td><p><strong>Create a deployment for suite:</strong></p><p>$CDF_HOME/bin/cdfctl deployment create -d $NAMESPACE</p><p>NOTE: This command creates a deployment with <strong>your original suite namespace</strong> as the deployment name.</p></td></tr><tr><td>6</td><td><p>Refine existing PVs</p></td><td>1 min</td><td><div><ol><li><p>Go to the <code>ESM_Helm_Chart-2x.x/scripts/transformation</code> directory.</p><p>cd ESM_Helm_Chart-2x.x/esm-1.0.0+2x.x-xxx/scripts/transformation</p></li><li><p>Run the following commands:</p><pre><code>chmod u+x refinePV.sh 
./refinePV.sh $SIZE
NOTE: Enter 2 'y' when execute the shell</code></pre></li><li><p>Run the following command to verify the PV creation.</p><pre><code>kubectl get pv|grep -E "config-volume|logging-volume|data-volume"|grep itsma</code></pre></li><li><p>Run the following command to verify the PV status is Available (Below command is supposed to return no result)</p><p>kubectl get pv|grep itsma|grep -v -E "db-volume|global-volume|smartanalytics"|awk '{if ($5!="Available") print $0}'</p></li></ol></div></td></tr><tr><td rowspan="2">7</td><td rowspan="2">Restore vault data<ul><li>Copy vault data from core-volume to global-volume</li><li>Copy vault secrets to the suite namespace</li></ul></td><td rowspan="2">5 mins</td><td><p><strong>Copy vault data from core-volume to global-volume</strong><br>On NFS server run:</p><p>sudo cp -R /mnt/efs/var/vols/itom/itsma/core/vault /mnt/efs/var/vols/itom/itsma/global-volume/<br>sudo chown -R $SYSTEM_USER_ID:$SYSTEM_GROUP_ID /mnt/efs/var/vols/itom/itsma/global-volume/vault</p></td></tr><tr><td><p><strong>Copy vault secrets to the suite namespace</strong></p><ol><li>Create script "copyVaultCredentials.sh" > <a href="https://docs.microfocus.com/doc/SMAX/24.2/TransformSmaxToHelmBased#Restore_vault_data">Restore_vault_data</a></li><li>Run below command<br>chmod u+x copyVaultCredentials.sh<br>./copyVaultCredentials.sh $NAMESPACE <releaseName></li></ol>NOTE: <strong>Replace <releaseName> with a unique release name that you want to specify for the suite deployment.</strong></td></tr><tr><td>8</td><td><p>Start OMT</p></td><td>5 mins</td><td><ol><li><strong>Start OMT:</strong><pre><code>$CDF_HOME/bin/cdfctl runlevel set -l UP -n core</code></pre></li><li><strong>Check that all the OMT pods are ready:</strong><pre><code>kubectl get pods -n core|grep -v 1/1|grep -v 2/2|grep -v 3/3|grep -v 4/4|grep -v Completed</code></pre></li></ol></td></tr><tr><td>9</td><td><p>Install the ESM helm chart</p><p>Create ingress for the suite (EKS only)</p></td><td>35 mins</td><td><p>Login Bastion and change folder to the ESM_Helm_Chart-2x.x/charts/ directory.<br><strong>Run the helm install command:</strong></p><p>helm install <releaseName> esm-1.0.0+2x.x-xxx.tgz -n $NAMESPACE -f values.yaml --set global.nodeSelector.Worker=label -f customized_values.yaml</p><p>NOTE: <strong>This release name is the one you gave in step 7</strong></p><p>During the helm installation, monitor the status of the itom-nginx-ingress service by running the below command:</p><p>kubectl get svc -n $NAMESPACE|grep itom-nginx-ingress-svc</p><p><strong>[EKS Only] Once the service is available, create the ingress for the suite & ingress for the SMAX integration.</strong></p><p>For example:</p><p>kubectl create -f sma-ingress.yaml<br>kubectl create -f sma-ingress-integration.yaml</p><p><strong>NOTE: The ingress yaml files are the ones you exported in Preparation - Step 3</strong></p><p><strong>Bound the newly created the ingress alb to Ops domain(**- <a href="http://smax.esm.com/">smax.esm.com</a>)</strong></p><p><strong>Add the newly created service port to the EKS worker's inbound security group</strong></p><p><strong>Reference:</strong></p><ul><li><ul><li>To create an ingress for the suite, see <a href="https://docs.microfocus.com/doc/SMAX/24.2/EKSDeploySuite#Create_an_Ingress_for_the_suite">Create an Ingress for the suite</a>.</li><li>For deployments with CMS integration, see <a href="https://docs.microfocus.com/doc/SMAX/24.2/IntegrationALBCms#Step_2/_Create_an_Ingress_for_SMAX_integration">Create a new CMS Ingress for SMAX integration</a>.</li><li>For deployments with OO integration, see <a href="https://docs.microfocus.com/doc/SMAX/24.2/ConfigureALBEKSOOC#Step_2/_Create_an_Ingress_for_SMAX_integration">Create a new OO Ingress for SMAX integration</a>.</li></ul></li></ul></td></tr><tr><td rowspan="2">10</td><td><p>Enable helm autopass</p></td><td>3 mins</td><td><ol><li><p>Log in to the control plane node or bastion node.</p></li><li>Change to the <code>ESM_Helm_Chart-2x.x/scripts/transformation</code> directory.</li><li><p>Change the permission of the updateAutopassKey.sh file:</p><p>chmod u+x updateAutopassKey.sh</p></li><li><p>Run the script to sync the autopass key.</p><p>./updateAutopassKey.sh -n $NAMESPACE</p><p>It will restart the <code>itom-bo-license-deployment</code> and <code>autopass-lm-v2</code> pods.</p></li><li><p>After the above pods are up and running, enter the autopass page with the new URL: https://<EXTERNAL_ACCESS_HOST>/autopass.</p></li></ol></td></tr><tr><td><p>Ensure all suite pods & job are ready</p></td><td>2 mins</td><td><p>Check helm install pod status</p><p>kubectl get pod -n $NAMESPACE|grep -v 1/1|grep -v 2/2|grep -v 3/3|grep -v 4/4|grep -v Completed</p><p>Kubectl get job -n $NAMESPACE</p></td></tr><tr><td rowspan="4"><h3>Post-tasks</h3></td><td><p>0</p></td><td><p>(Optional) Reinstall lost services:</p><p>Toolkit,</p><p>Monitoring,</p><p>Opentelemetry</p></td><td></td><td></td><td><p><strong>After install the helm version suite, certain ports in suite will be reset. We have to re-enable them again in suite. Please run following command"</strong></p><p><strong>1.Run the following patch command:</strong></p><p>kubectl patch svc idm-svc -n $(kubectl get namespace |grep itsma | cut -f1 -d " ") --type=json -p='[{"op":"add","path":"/spec/ports/2","value":{"name":"ssl","port":443,"protocol":"TCP","targetPort":8443}},{"op":"add","path":"/spec/ports/3","value":{"name":"metrics","port":444,"protocol":"TCP","targetPort":8444}}]'#expose nginx portkubectl patch svc itom-nginx-ingress-svc -n $(kubectl get namespace |grep itsma | cut -f1 -d " ") --type=json -p='[{"op":"add","path":"/spec/ports/1","value":{"name":"http-metrics","port":10254,"protocol":"TCP","targetPort":10254}}]'#expose redis portkubectl patch svc itom-xruntime-redis-svc -n $(kubectl get namespace |grep itsma | cut -f1 -d " ") --type=json -p='[{"op":"add","path":"/spec/ports/1","value":{"name":"https-metrics","port":9121,"protocol":"TCP","targetPort":9121}}]'#expose rabbitmq port#kubectl patch svc itom-xruntime-rabbitmq-svc -n $(kubectl get namespace |grep itsma | cut -f1 -d " ") --type=json -p='[{"op":"add","path":"/spec/ports/4","value":{"name":"http-metrics","port":9419,"protocol":"TCP","targetPort":15691}}]'#expose port for JMX platformkubectl patch svc itom-xruntime-platform-svc -n $(kubectl get namespace |grep itsma | cut -f1 -d " ") --type=json -p='[{"op":"add","path":"/spec/ports/3","value":{"name":"platform-metrics","port":5555,"protocol":"TCP","targetPort":5555}}]'kubectl patch svc itom-xruntime-platform-offline-svc -n $(kubectl get namespace |grep itsma | cut -f1 -d " ") --type=json -p='[{"op":"add","path":"/spec/ports/3","value":{"name":"platform-offline-metrics","port":5555,"protocol":"TCP","targetPort":5555}}]'kubectl patch svc itom-xruntime-platform-offline-ng-svc -n $(kubectl get namespace |grep itsma | cut -f1 -d " ") --type=json -p='[{"op":"add","path":"/spec/ports/3","value":{"name":"platform-offline-ng-metrics","port":5555,"protocol":"TCP","targetPort":5555}}]'kubectl patch svc itom-xruntime-platform-readonly-svc -n $(kubectl get namespace |grep itsma | cut -f1 -d " ") --type=json -p='[{"op":"add","path":"/spec/ports/3","value":{"name":"platform-readonly-metrics","port":5555,"protocol":"TCP","targetPort":5555}}]'#expose port for JMX gatewaykubectl patch svc itom-xruntime-gateway-svc -n $(kubectl get namespace |grep itsma | cut -f1 -d " ") --type=json -p='[{"op":"add","path":"/spec/ports/3","value":{"name":"gateway-metrics","port":5555,"protocol":"TCP","targetPort":5555}}]'#expose port for JMX service portalkubectl patch svc itom-xruntime-serviceportal-svc -n $(kubectl get namespace |grep itsma | cut -f1 -d " ") --type=json -p='[{"op":"add","path":"/spec/ports/3","value":{"name":"serviceportal-metrics","port":5555,"protocol":"TCP","targetPort":5555}}]'</p><p><strong>2.Go to <a href="https://www.microfocus.com/marketplace/itom/content/service-management-automation-monitor">ITOM Marketplace</a> to download all Service Monitor definitions</strong></p><p><strong>3.Unzip the package and navigate to the folder prometheus/servicemonitor and run the following command:</strong></p><p>namespace=`kubectl get namespace |grep itsma| cut -f1 -d " "`<br>sed -i -e 's/<namespace>/'$namespace'/g' *.yaml</p><p>sed -i -e 's/insecureSkipVerify: false/insecureSkipVerify: true/g' *.yaml<br>kubectl delete -f./<br>kubectl create -f./</p></td></tr><tr><td>1</td><td><p>Clean up unused pods in the OMT namespace</p></td><td>5 mins</td><td rowspan="3">NA</td><td><p><strong>Run the following command to remove cdf-apiserver, cdfapiserverdb, frontendIngress, itom-frontend-ui, and itom-mng-portal resources:</strong></p><p>helm upgrade apphub $CDF_HOME/charts/apphub-1.2*.tgz --reuse-values --set global.services.suiteDeploymentManagement=false -n core</p><p>kubectl delete deploy suite-conf-pod-itsma -n core --ignore-not-found=true</p><p>kubectl delete svc suite-conf-svc-itsma -n core --ignore-not-found=true</p><p>kubectl delete ingress suite-conf-ing-itsma -n core --ignore-not-found=true</p><p>If you are restoring a single namespace after running above command, it will fail, please do workaround with below wiki:</p><p><a href="https://rndwiki.houston.softwaregrp.net/confluence/display/SMA/Fix+cdf+issue+no+found+clusterrolebinding+and+clusterrole">OMT clusterrolebinding and clusterrole</a></p><p>After helm transformation, OMT 5443 portal will no longer be in use.</p><p><br><strong>Run the following command to clean up OMT install portal ingress for ALB controller:</strong></p><pre><code>kubectl delete ingress -n core -l app=install-ingress</code></pre></td></tr><tr><td>2</td><td><p>Delete unused PVs</p></td><td>1 mins</td><td><pre><code>kubectl delete pv $NAMESPACE-db-volume
kubectl delete pv $NAMESPACE-smartanalytics-volume
kubectl delete pv $NAMESPACE-global-volume</code></pre></td></tr><tr><td>3</td><td><p>Delete unused nfs folders</p></td><td>15 mins</td><td><p>Run the following command to clean unused nfs folder:</p><p>dbVolume=<dbVolumePath></p><p>globalVolume=<globalVolumePath></p><p>smartanalyticsVolume=<smartaVolumePath></p><p>Where: <code><dbVolumePath></code> <code><globalVolumePath></code> and <code><smartaVolumePath></code> are the NFS paths of db-volume, global-volume, and smartanalytics-volume, respectively.</p><p>For example:</p><p>dbVolume=/mnt/efs/var/vols/itom/itsma/db-volume</p><p>globalVolume=/mnt/efs/var/vols/itom/itsma/global-volume</p><p>smartanalyticsVolume=/mnt/efs/var/vols/itom/itsma/smartanalytics-volume</p><p><br>sudo rm -rf $dbVolume<br>sudo rm -rf $smartanalyticsVolume<br>sudo rm -rf $globalVolume/data<br>sudo rm -rf $globalVolume/image<br>sudo rm -rf $globalVolume/resources<br>sudo rm -rf $globalVolume/config<br>sudo rm -rf $globalVolume/certificate<br>sudo rm -rf $globalVolume/tenant-export<br>sudo rm -rf $globalVolume/tenant-import<br>sudo rm -rf $globalVolume/jdbc<br>sudo rm -rf $globalVolume/l10n<br>sudo rm -rf $globalVolume/va/configs<br>sudo rm -rf $globalVolume/va/stopwords<br>sudo rm -rf $globalVolume/di<br>sudo rm -rf $globalVolume/logs</p></td></tr><tr><td rowspan="4"><h3>Verification</h3></td><td>1</td><td>SMAX</td><td rowspan="4">30 mins</td><td rowspan="4">NA</td><td rowspan="4"></td></tr><tr><td>2</td><td>NSACM Sanity</td></tr><tr><td>3</td><td>Audit Sanity</td></tr><tr><td>4</td><td>Audit-Collector Sanity</td></tr></tbody></table>

#### Doc Link:

[Transform SMAX To Helm](https://docs.microfocus.com/doc/SMAX/24.2/TransformSmaxToHelmBased#Clean_up_unused_pods_in_the_OMT_namespace)

**Related pages**

- Page:
	[ESM Cloud Farm Version Tracking](/display/ICSD/ESM+Cloud+Farm+Version+Tracking)
- Page:
	[How to get an Opentext Confluence account](/display/ICSD/How+to+get+an+Opentext+Confluence+account)
- Page:
	[ITOM APM AppPluse Cloud Farm Information](/display/ICSD/ITOM+APM+AppPluse+Cloud+Farm+Information)
- Page:
	[ITOM Cloud Service Ops Doc Management Process](/display/ICSD/ITOM+Cloud+Service+Ops+Doc+Management+Process)
- Page:
	[ITOM ESM Cloud Service Catalog](/display/ICSD/ITOM+ESM+Cloud+Service+Catalog)
- Page:
	[ITOM OpsB NOM Cloud Service Catalog](/display/ICSD/ITOM+OpsB+NOM+Cloud+Service+Catalog)
- Page:
	[OpsB and NOM Cloud Deployments Version Tracking](/display/ICSD/OpsB+and+NOM+Cloud+Deployments+Version+Tracking)
