-
-
-
-
Ingress
-
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!
Ingress
Every Citrix SecurSpaces™ deployment needs an ingress controller in front of it. The platform terminates TLS at the ingress, and workspace traffic — including WebSocket connections for the Cloud IDE and, optionally, SSH — passes through it.
Supported controllers
| Controller | Deployed by the SecurSpaces chart | Configuration needed |
|---|---|---|
| NetScaler CPX (recommended) | Yes | None. See NetScaler CPX |
| NGINX | No | Tuning values, and manual setup for SSH |
| HAProxy | No | Set the ingress class |
| Kubernetes Gateway API | No | Set a gateway class instead of using Ingress resources |
NetScaler CPX is the recommended choice, and the only one the SecurSpaces chart can deploy and configure for you. If you have no existing preference, use it.
Important:
NetScaler CPX does not currently work on Google GKE. This is a known issue with a fix in progress and no date yet. On GKE, use NGINX or the Kubernetes Gateway API, and contact Citrix for the current status. See Google GKE.
What the choice affects
Two things differ meaningfully between controllers.
WebSocket and HTTP/2 handling. The Cloud IDE holds a WebSocket connection for as long as a workspace is open. A controller that closes idle connections early, or buffers responses aggressively, produces disconnects that look like platform faults. With NetScaler CPX the chart applies the right profiles itself. With NGINX you set them by hand — see NGINX.
SSH access to workspaces. SSH needs a TCP path through the ingress, on a port other than 443.
- With NetScaler CPX, the chart creates the SSH ingress and the service port for you. Nothing to do.
- With NGINX, you create a ConfigMap, patch the controller deployment, and expose the port yourself. See SSH TCP forwarding with NGINX.
That difference is the main practical reason to prefer NetScaler CPX.
Selecting a controller
The controller is chosen in the configuration file the installer generates, before you run Helm. See Install with the Strong Installer CLI.
| Setting | Purpose |
|---|---|
platform.ingressClass |
The ingress class your controller watches |
platform.useNetscalerController |
Deploy and configure NetScaler CPX |
platform.useNginxController |
Apply NGINX-specific ingress annotations |
platform.useHAProxyController |
Apply HAProxy-specific ingress annotations |
platform.useGatewayAPI |
Use Gateway API resources instead of Ingress resources |
Set the annotation flag that matches your controller. ingressClass must match the class the controller
actually watches — confirm it with kubectl get ingressclass rather than assuming the default.
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.