-
Getting started
-
-
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 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!
Getting started
This guide helps you to quickly evaluate NetScaler Ingress Controller for Kubernetes if you are new to NetScaler Ingress Controller. If you are an advanced user, see What is Next.
Before you begin
Ensure that you have installed and set up a Minikube cluster.
Getting started with NetScaler Ingress Controller
In this procedure you perform the following steps:
- Deploy NetScaler CPX (a containerized version of NetScaler) along with ingress controller
- Deploy
Guestbook
, a sample application - Deploy Ingress rules to route traffic to the
Guestbook
application - Send some traffic to the application and verify
Deploy NetScaler CPX with NetScaler Ingress Controller
Perform the following to deploy NetScaler CPX with NetScaler Ingress Controller.
-
Deploy NetScaler CPX as an Ingress proxy in the Minikube cluster.
kubectl create -f https://raw.githubusercontent.com/citrix/cloud-native-getting-started/master/beginners-guide/manifest/cpx.yaml
-
Verify the installation using the following command.
kubectl get pods -l app=cpx-ingress
Deploy a sample application
In this step, you deploy Guestbook
which is a multi-tier PHP-based web application that uses Redis.
-
Deploy the
Guestbook
application in Minikube.kubectl create -f https://raw.githubusercontent.com/citrix/cloud-native-getting-started/master/beginners-guide/manifest/guestbook-app.yaml
-
Verify the installation using the following:
kubectl get pods -l 'app in (guestbook, redis)'
Deploy an Ingress for the sample application
To deploy ingress rules for the sample application and verify the functionality, perform the following steps.
-
Deploy an Ingress rule that sends traffic to the
Guestbook
application(http://www.guestbook.com).kubectl create -f https://raw.githubusercontent.com/citrix/cloud-native-getting-started/master/beginners-guide/manifest/guestbook-ingress.yaml
-
Verify the Ingress deployment using the following command.
kubectl get ingress
-
Display information about the service using the following command.
kubectl get svc cpx-service # kubectl get service cpx-service NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE cpx-service NodePort 10.106.123.144 <none> 80:30592/TCP,443:31338/TCP 43m
You can get the NodePort information from this example, 30592 and 31338 are NodePorts.
-
Send traffic to the
Guestbook
microservice application and verify that traffic to this URL gets theGuestbook
page:curl -s -H \"Host: www.guestbook.com\" http://<MiniKube-IP-address>:<NodePort> | grep Guestbook
Expected output:
<title>Guestbook</title> <h2>Guestbook</h2>
Note:
You can get the Minikube IP address using the
minikube ip
command. You can also use theminikube service cpx-service --url
command to directly get the URL used in the cURL command.
What is next
The getting started section helps a beginner to evaluate NetScaler Ingress Controller quickly and the installation covers only the basic functionality. You can see the following topics for comprehensive information on deploying NetScaler Ingress Controller and customize your installation accordingly.
- Deployment topologies: Provides information on various topologies supported by NetScaler Ingress Controller.
- Supported platforms: Provides information about the different platforms supported including bare metal and cloud platforms.
- Deploy NetScaler Ingress Controller: Provides information on how to deploy NetScaler Ingress Controller for different flavors of NetScaler like NetScaler CPX, VPX, and MPX.
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.