Hi Amr_Salah,

This type of change is all done on the Azure side. So any AKS CIDR update is all handled by the AKS Platform and should have no impact on the SMAX side. The process to do this is normally covered off by the AKS documentation.

I think whenever you are looking at doing this sort of change its wise to make sure all your SMAX application is fully backed up and you've got your recovery processes in place. Then if the worst case scenario happened, you know your system can at least be restored.

Thanks Dave

i agree with you that it will be done on AKS side, but I'm afraid of affecting this on the SMAX performance as this will directly hit the services IPs, so do you think it is that straight forward, stop core and itsma services and do the action then update 

do you have any recommendation to back up the SMAX application in this case, shall we use velero ?

Hi Amr,

Basically that is the recommended approach. I've not heard of any other approach for this particular type Change you want to implement. In regards to backup I'd suggest using the below guide especially as you are working in Azure:

https://docs.microfocus.com/doc/SMAX/25.1/SmaBackupProcedure#Back_up_the_suite_on_Azure

I'd also recommend trying to make sure you can verify your backup and restore process before implementing the change. Then you know you can get everything back. Not just that, it's good practice to test backup and restore procedures every so often to make sure everything works, before you hit any unexpected issues :-)