Hi ​@DavidSmile,

If global.replicas is omitted during IFS Cloud installation, the Helm charts use their default settings—typically 1 replica per service. This may be fine for test setups but not ideal for production due to:

• No High Availability: No redundancy if a pod fails.

•  Limited Scalability: Can't handle high load efficiently.

Best Practice: Set it explicitly in ifscloud-values.yaml:

global: replicas: 2

This applies across all scalable services. You can still override individual components like:

ifsappodata: replicas: 3

Only pods for the active modules (via solutionset.yaml) are deployed. Others should have their replicas set to 0 if left inactive.

eg:

 # BUSMOD component 
 ifsapp-busmod

 # MXCORE component
 ifsmaintenix-appserver

 ifsmaintenix-reportserver

 # PBIES component
 ifsapp-powerbi-svc

 # RMPANL component
 ifsapp-rmpanel

 ifsapp-rmsync

 # FNDREM component
 ifsapp-rem

 # CRYSTL component
 ifsapp-reporting-cr

More  info: https://docs.ifs.com/techdocs/25r1/070_remote_deploy/010_installing_fresh_system/010_planning_installation/007_middle_tier/010_overview/#containerspods_in_the_ifs_cloud_middle_tier

Regards,

Binuri

Thank you, ​@binuriJ  !