-
-
-
Deploy NetScaler ingress controller with OpenShift router sharding support
-
Deploy NetScaler CPX as an Ingress in Azure Kubernetes Engine
-
Deploy NetScaler ingress controller in an Azure Kubernetes Service cluster with NetScaler VPX
-
Deploy NetScaler ingress controller for NetScaler with admin partitions
-
Multi-cloud and GSLB solution with Amazon EKS and Microsoft AKS clusters
-
-
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
-
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!
Upgrade NetScaler Operator
To upgrade NetScaler Operator to version 3.1.2 from earlier versions, perform the following steps:
-
Back up YAMLs of all the installed controllers, such as NSIC, GSLB, and NSOE, by using the following command:
for crd in $(oc get crds -o jsonpath='{.items[*].metadata.name}' | tr ' ' '\n' | grep 'netscaler.com'); do echo "Getting instances for CRD: $crd"; oc get $crd --all-namespaces -o yaml >> "all_controller_crd_instances.yaml"; done <!--NeedCopy-->
-
Back up the
citrix.com
CRD instances managed by NSIC and GSLB controller to a YMAL file by using the following command:for crd in $(oc get crds -o jsonpath='{.items[*].metadata.name}' | tr ' ' '\n' | grep 'citrix.com'); do echo "Getting instances for CRD: $crd"; kubectl get $crd --all-namespaces -o yaml >> "all_citrix_crd_instances.yaml"; done <!--NeedCopy-->
-
Remove
citrix.com
CRDs by using the following command:$(oc get crds -o jsonpath='{.items[*].metadata.name}' | tr ' ' '\n' | grep 'citrix.com'); do oc delete crd $crd; done <!--NeedCopy-->
-
Delete all the controller instances within NetScaler Operator.
Important
The Delete all operand instances for this operator option displayed as part of the Operator deletion workflow might not work sometimes and some residual components are not deleted. Follow the steps mentioned here to avoid conflicts.
-
Navigate to Operators > Installed Operators and click NetScaler Operator.
-
Click All instances to list all the controller instances.
-
To delete each controller instance, click the ellipses icon next to a controller and then click Delete.
In the following example, a NetScaler CPX with NetScaler Ingress Controller instance is deleted.
-
Click Delete to confirm deleteion.
-
-
Remove netscaler.com CRDs of NetScaler Operator (NSIC, NSIC+CPX, and NSOE) by using the following command:
for crd in $(oc get crds -o jsonpath='{.items[*].metadata.name}' | tr ' ' '\n' | grep 'netscaler.com'); do echo "Deleting CRD: $crd" oc delete crd $crd done <!--NeedCopy-->
-
To uninstall NetScaler Operator, navigate to Operators > Installed Operators, click the ellipses icon next to NetScaler Ingress Controller Operator, and then click Uninstall Operator.
-
Click Uninstall to confirm uninstallation.
-
Convert the controller YAMLs you backed up in step 1 to the new schema introduced in NetScaler Operator 3.1.2. To do so, for each parameter in the controller YAML, check the respective modified parameter in the new schema and update the YAMLs accordingly. For information on parameters in NetScaler Operator version 3.1.2, see NetScaler Operator.
-
Deploy NetScaler Operator. For information on deploying NetScaler Operator, see Deploy NetScaler Operator.
-
Install the controllers one after the other with the YAMLs updated in step 8. For more information, see NetScaler Operator.
-
Install the CRDs backed up in step 2 by using the following command:
oc apply -f all_citrix_crd_instances.yaml <!--NeedCopy-->
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.