-
-
-
-
-
Nutanix Kubernetes Platform
-
-
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!
Nutanix Kubernetes Platform
Citrix SecurSpaces™ runs on the Nutanix Kubernetes Platform (NKP). This page covers what is specific to NKP: the cluster prerequisites, the node labels, the certificate, and the ingress settings the chart needs.
Everything after that is the standard installation. When you have finished here, continue with Install with the Strong Installer CLI.
Nutanix publishes a full end-to-end walkthrough as a solutions tech note, which is useful for the NKP side of the deployment: Citrix Secure Developer Spaces on Nutanix Kubernetes Platform.
Important:
The Nutanix tech note was written against SecurSpaces
2025.10.13and has not been revised since. Its installer image tag, chart file name, and CLI command are all out of date — it usesstrong-cli, which is nowsds-cli. Use it for the NKP-specific steps, and follow the SecurSpaces documentation for the installation itself.
Prerequisites
- NKP 2.17 or later, deployed as either a self-managed or a workload cluster.
- A free IP address in the Kubernetes service load balancer range, for the SecurSpaces load balancer.
- A kubeconfig with privileged access to the cluster.
-
Three domain names:
Purpose Example Primary sds.example.comProxy proxy.sds.example.comWildcard subdomain *.proxy.sds.example.com - A TLS certificate whose Subject Alternative Names cover all three domains.
- A SecurSpaces platform license.
For supported Kubernetes versions and capacity planning, see System requirements and Sizing.
Create the namespace
kubectl create namespace strong-network
<!--NeedCopy-->
Label the nodes
SecurSpaces separates service nodes from workspace nodes. Label them so the chart can schedule each pod type on the right pool:
kubectl label nodes <service-node-name> strong.network/type=service
kubectl label nodes <workspace-node-name> strong.network/type=workspace
<!--NeedCopy-->
For how many nodes of each type to provision, see Sizing.
Install the certificate
Store the certificate and its private key as a TLS secret in the namespace:
kubectl create secret tls sds-example-com-cert \
--key=/path/to/private_key.pem \
--cert=/path/to/cert.pem \
-n strong-network
<!--NeedCopy-->
If you use cert-manager, request the certificate instead. This example issues a self-signed certificate, which is suitable for testing but not for production:
apiVersion: cert-manager.io/v1
kind: Certificate
metadata:
name: sds-example-com-cert
namespace: strong-network
spec:
secretName: sds-example-com-cert
issuerRef:
name: selfsigned-issuer
kind: ClusterIssuer
dnsNames:
- sds.example.com
- proxy.sds.example.com
- "*.proxy.sds.example.com"
<!--NeedCopy-->
Configure the chart for NKP
Run the installer as described in Install with the Strong Installer CLI. Select Percona MongoDB when the installer asks for the database type, unless you are using an external database.
Then add the NKP-specific values to the generated configuration file. NKP ships NetScaler CPX as its ingress controller, so the chart needs telling to emit NetScaler ingress annotations:
platform:
useNetscalerController: true
ingressClass: netscaler-cpx-ingress
sslCertificateSecret: sds-example-com-cert
<!--NeedCopy-->
ingressClass must match the class your NetScaler CPX controller actually watches. The chart default is
netscaler-cpx-ingress; confirm yours with kubectl get ingressclass and set both sides to the same value.
Note:
If your chart version requires node affinity to be switched on explicitly, also set
platform.enableNodeAffinity: true. The node labels above have no effect unless affinity is enabled. The Nutanix tech note marks this as required for2025.10.13.
Deploy
helm upgrade --install \
--namespace strong-network \
--create-namespace \
-f ./config_<version>.yaml \
release ./ninjachart-<version>.tgz
<!--NeedCopy-->
Check that the platform came up:
kubectl get pods -n strong-network
kubectl get ingress -n strong-network
<!--NeedCopy-->
Then open https://sds.example.com/login and sign in with the administrator account you set during
installation.
Related information
Share
Share
This Preview product documentation is Citrix Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Citrix 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 Citrix product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.