-
-
NetScaler GSLB controller for applications deployed in distributed Kubernetes clusters
-
-
Deploy NetScaler ingress controller with OpenShift router sharding support
-
Deploy NetScaler ingress controller using OpenShift Operator
-
Deploy NetScaler Observability Exporter using OpenShift Operator
-
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
-
-
TCP profile support for services of type LoadBalancer
-
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!
TCP profile support for services of type LoadBalancer
This topic contains information on how to apply TCP profiles for services of type LoadBalancer
. TCP profile support for service of type LoadBalancer
is similar to TCP profile support on Ingress.
For information on TCP profile support on Ingress, see TCP profile support on Ingress.
A TCP profile is a collection of TCP settings. Instead of configuring the settings on each entity, you can configure TCP settings in a profile and bind the profile to all the required entities.
The NetScaler Ingress Controller provides the following service annotations for TCP profile for services of type LoadBalancer
. You can use these annotations to define the TCP settings for the NetScaler.
Service annotation | Description |
---|---|
service.citrix.com/frontend-tcpprofile |
Use this annotation to create the front-end TCP profile (Client Plane). |
service.citrix.com/backend-tcpprofile |
Use this annotation to create the back-end TCP profile (Server Plane). |
User-defined TCP profiles
Using service annotations for TCP, you can create custom profiles with name same as cs virtual server or service group and bind to the corresponding virtual server(frontend-tcpprofile
) and service group (backend-tcpprofile
).
Service annotation | Sample |
---|---|
service.citrix.com/frontend-tcpprofile |
service.citrix.com/frontend-tcpprofile: '{"ws":"enabled", "sack" : "enabled"}' |
service.citrix.com/backend-tcpprofile |
service.citrix.com/backend-tcpprofile: '{"ws":"enabled", "sack" : "enabled"}' |
Built-in TCP profiles
Built-in TCP profiles do not create any profile and bind a given profile name in annotation to the corresponding virtual server(frontend-tcpprofile) and service group(backend-tcpprofile).
Following are examples for built-in TCP profiles.
service.citrix.com/frontend-tcpprofile: "tcp_preconf_profile"
service.citrix.com/backend-tcpprofile: '{"citrix-svc":"tcp_preconf_profile"}
Example: Service of Type load balancer with the TCP profile configuration
In this example, TCP profiles are configured for a sample application tea-beverage
. This application is deployed and exposed using a service of type LoadBalancer using the tea-profile-example.yaml file.
For step by step instruction for exposing services of type LoadBalancer
, see service of type LoadBalancer
.
Following is a snippet of the service configuration with TCP profile.
apiVersion: v1
kind: Service
metadata:
name: tea-beverage
annotations:
service.citrix.com/secure_backend: '{"443-tcp": "True"}'
service.citrix.com/service_type: 'SSL'
service.citrix.com/backend-tcpprofile: '{"ws":"ENABLED", "sack" : "enabled"}'
service.citrix.com/frontend-tcpprofile: '{"ws":"ENABLED", "sack" : "enabled"}'
spec:
type: LoadBalancer
loadBalancerIP: 10.105.158.194
ports:
- name: tea-443
port: 443
targetPort: 443
selector:
name: tea-beverage
Note:
The TCP profile is supported for single port services.
Share
Share
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.