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à))
Deploy Citrix API gateway using Red Hat OpenShift Operators
OpenShift Operator is an open-source toolkit designed to package, deploy, and manage Kubernetes native applications in a more effective, automated, and scalable way.
An API gateway acts as the single entry point for your APIs and ensures secure and reliable access to multiple APIs and microservices in your system. Citrix provides an enterprise grade API gateway for North-South API traffic into the OpenShift cluster. The API gateway integrates with the OpenShift cluster through the Citrix ingress controller and the Citrix ADC (Citrix ADC MPX, VPX, or CPX) deployed as the Ingress Gateway for on-premises or cloud deployments.
This topic covers information on how to deploy the API gateway using OpenShift Operators.
The Citrix API gateway operator installs the CRDs required for the API Gateway functionality. Since this operator leverages the Citrix ingress controller, you need to create an instance of the API Gateway CRD, which is the Citrix ingress controller. If you already have a Citrix ingress controller instance in the cluster you need to install it again.
API gateway supports the following CRDs:
Auth CRD (authpolicies.citrix.com)
Authentication policies are used to enforce access restrictions to resources hosted by an application or an API server.
Content routing CRDs (httproutes.citrix.com and listeners.citrix.com)
Kubernetes native Ingress supports only basic host and path based routing. Using content routing CRDs, you can expose the advanced content routing abilities provided by Citrix ADC like routing based on header values or query strings.
Rate limit CRD (ratelimits.citrix.com) In a Kubernetes deployment, you can rate limit the requests to the resources on the back end server or services using the rate limiting feature provided by the ingress Citrix ADC.
Rewrite and responder CRD (rewritepolicies.citrix.com) In a Kubernetes environment, to deploy specific layer 7 policies (such as redirecting HTTP traffic to a specific URL) requires you to add appropriate libraries within the microservices and manually configure the policies. Instead, you can use the Rewrite and Responder features provided by the Ingress Citrix ADC device to deploy these policies.
VIP CRD (vips.citrix.com)
Citrix provides a VIP CRD for asynchronous communication between the IPAM controller and the Citrix ingress controller. The IPAM controller is provided by Citrix for IP address management.
Perform the following steps to deploy the API gateway using the OpenShift Operator.
In the OperatorHub, search for Citrix API Gateway Operator.
Select the Citrix API Gateway Operator, and click Install.
Choose the namespace where you want the operator to be installed and click Subscribe.
Once the Citrix API gateway operator is installed, you can see it listed under the Installed Operators section on the left panel. At this point, all CRDs are installed in the cluster.
To create instances of each CRD, select the appropriate CRD and click Create Instance.
Once you create the instance you can see all your instances by selecting the All instances tab.
To update any values of the created CRD instance, click the instance and go to the YAML tab and edit the YAML file and click Save.
For more information on upgrading CRD versions, see the OpenShift documentation.
To delete an instance of the CRD you have to delete the Citrix ingress controller instance from the user interface. Select the three vertical dots on the right side of the instance as shown in the following image and then click Delete CitrixIngressController.
To delete the operator, click the Actions drop-down list and then click Uninstall operator.
Make sure that all instances are deleted manually before uninstalling the operator. The instances are not automatically deleted if you uninstall the operator.
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 Do Not Agree to exit.