-
-
SSL certificate for services of type LoadBalancer through the Kubernetes secret resource
-
BGP advertisement for type LoadBalancer services and Ingresses using NetScaler CPX
-
NetScaler CPX integration with MetalLB in layer 2 mode for on-premises Kubernetes clusters
-
Advanced content routing for Kubernetes Ingress using the HTTPRoute CRD
-
IP address management using the NetScaler IPAM controller for Ingress resources
-
Deploy NetScaler ingress controller for NetScaler with admin partitions
-
-
-
NetScaler CPX configuration persistence during upgrade
-
This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
NetScaler CPX configuration persistence during upgrade
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.
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
<!--NeedCopy-->
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
<!--NeedCopy-->
If NetScaler CPX is on version 13.1, set enableStartupProbe to false.
Share
Share
In this article
This Preview product documentation is Cloud Software Group Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Cloud Software Group Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Cloud Software Group product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.