NetScaler CPX configuration persistence during upgrade

Last published : Sep 30, 2026
When a NetScaler® CPX pod restarts during a Helm upgrade, a rolling update, or any other pod replacement, the running configuration accumulated through ingress and service resources is not persisted. The NetScaler Ingress Controller (NSIC) must then re-push every resource from scratch through the NITRO API. In large-scale ingress deployments, this reconciliation can take a longer time before NetScaler CPX is ready to handle traffic.
The NetScaler CPX configuration persistence eliminates this delay by saving the NetScaler CPX running configuration to a Kubernetes ConfigMap at pod shutdown. The running configuration is automatically restored when the replacement pod starts. The new pod comes up with most configurations pre-loaded and therefore, the time taken for the new pod to go live is reduced. This feature is supported from NetScaler Ingress Controller version 4.1.x onwards.
Related information
Upgrade and troubleshooting

Benefits

  • Near-instant configuration restore after pod restarts or upgrades.
  • No manual intervention required — backup and restore are fully automated.
  • Compatible with existing Helm chart workflows (helm upgrade).
  • Handles large configurations through automatic overflow compression.
  • No changes required to NetScaler CPX itself — uses the native NetScaler CPX bootup configuration mechanism.

Enable configuration persistence

Helm installation

Enable the feature by setting cpxConfigPersistenceEnabled=true during install or upgrade:
helm install my-release netscaler/netscaler-cpx-with-ingress-controller --set cpxConfigPersistenceEnabled=true,license.accept=yes
Or
Enable the feature by setting cpxConfigPersistenceEnabled=true on an existing release:
helm upgrade my-release netscaler/netscaler-cpx-with-ingress-controller \
  --set cpxConfigPersistenceEnabled=true,license.accept=yes
If NetScaler CPX is on version 13.1, set enableStartupProbe to false.