# Toggle-plaftform-offline-NG-for-Native-SACM_686073929
## Introduction

The platform offline NG pod introduced in version 24.2 aims to address resource bottlenecks encountered during a-synced job handling, such as a job for Native SACM CI notifications. It's designed to handle high incoming loads, particularly during peak times when a large number of CIs are received from UCMDB, aiming to distribute the Native SACM CI sync task load from the current offline pod.

By default, Native SACM relies on this pod to work. If you want, you can disable it so that Native SACM switches back to the original offline pod to process CIs. You can also enable it again after you disable it.

## Disable Native SACM CI sync from UCMDB via Offline NG

Perform the following steps on the bastion node:

1. Edit the configmap:
	`kubectl edit cm itom-xruntime-infra-config -n $(kubectl get namespace |grep itsma | cut -f1 -d " ")`
2. Update this parameter:  
	`ENABLE_SCALABLE_NATIVE_SACM: "false"`
3. Restart the offline and offline-ng pods:
	`kubectl rollout restart deployment itom-xruntime-platform-offline-ng  -n $(kubectl get namespace |grep itsma | cut -f1 -d " ")`  
	`kubectl scale deployment itom-xruntime-platform-offline -n $(kubectl get namespace |grep itsma | cut -f1 -d " ") --replicas=0` `   kubectl scale deployment itom-xruntime-platform-offline -n $(kubectl get namespace |grep itsma | cut -f1 -d " ") --replicas=1`

## Enable Native SACM CI sync from UCMDB via Offline NG

Perform the following steps on the bastion node:

1. Edit the configmap:
	`kubectl edit cm itom-xruntime-infra-config ` `-n $(kubectl get namespace |grep itsma | cut -f1 -d " ") `
2. Update this parameter:  
	`ENABLE_SCALABLE_NATIVE_SACM: "true"`
3. Restart the offline and offline-ng pods:  
	`kubectl rollout restart deployment itom-xruntime-platform-offline-ng  -n $(kubectl get namespace |grep itsma | cut -f1 -d " ")`  
	`kubectl scale deployment itom-xruntime-platform-offline -n $(kubectl get namespace |grep itsma | cut -f1 -d " ") --replicas=0` `   kubectl scale deployment itom-xruntime-platform-offline -n $(kubectl get namespace |grep itsma | cut -f1 -d " ") --replicas=1`
4. Check the replicas of the offline-ng pod, and change it to 1 if it is not:  
	`kubectl scale deployment itom-xruntime-platform-offline-ng -n $(kubectl get namespace |grep itsma | cut -f1 -d " ") --replicas=1`
