使用Red Hat OpenShift Operator部署Citrix API网关：基于Citrix博客的实战教程

Red Hat’s OpenShift Operator is an open-source toolkit designed to package, deploy, and manage Kubernetes-native applications in a more effective, automated, and scalable way.

红帽的OpenShift Operator是一个开源工具包，旨在以更有效，自动化和可扩展的方式打包，部署和管理Kubernetes本地应用程序。

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 (MPX, VPX, or CPX) deployed as the ingress gateway for on-premises or cloud deployments.

API网关充当API的单一入口点，并确保对系统中的多个API和微服务的安全可靠访问。 Citrix为向OpenShift集群的南北API流量提供了企业级API网关 。 API网关通过Citrix Ingress Controller和Citrix ADC (MPX，VPX或CPX)与OpenShift群集集成，该Citrix ADC被部署为本地或云部署的入口网关。

In this blog post, I’ll look at how you can deploy the API gateway using OpenShift Operators.

在此博客文章中，我将介绍如何使用OpenShift运算符部署API网关。

The Citrix API gateway operator installs the custom resource definitions (CRDs) required for the API Gateway functionality. Because 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.

Citrix API网关操作员将安装API网关功能所需的自定义资源定义(CRD)。 因为该运营商利用思杰入口控制器，你需要创建API网关CRD，这是思杰入口控制器的一个实例。 如果群集中已经有一个Citrix Ingress Controller实例，则需要重新安装它。

API Gateway supports the following CRDs:

API网关支持以下CRD：

• Auth CRD (authpolicies.citrix.com): Authentication policies are used to enforce access restrictions to resources hosted by an application or an API server. 身份验证CRD(authpolicies.citrix.com)：身份验证策略用于对应用程序或API服务器托管的资源实施访问限制。
• 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. 内容路由CRD(httproutes.citrix.com和listeners.citrix.com)： Kubernetes本地入口仅支持基本的主机和基于路径的路由。 使用内容路由CRD，您可以公开Citrix ADC提供的高级内容路由功能，例如基于标头值或查询字符串的路由。
• 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. 速率限制CRD( ratelimits.citrix.com )：在Kubernetes部署中，您可以使用入口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. 重写和响应者CRD(rewritepolicies.citrix.com)：在Kubernetes环境中，要部署特定的第7层策略(例如将HTTP流量重定向到特定的URL)，需要在微服务中添加适当的库并手动配置策略。 相反，您可以使用入口Citrix ADC设备提供的“重写和响应程序”功能来部署这些策略。
• 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. VIP CRD(vips.citrix.com)： Citrix为IPAM控制器和Citrix Ingress Controller之间的异步通信提供了VIP CRD。 Citrix为IP地址管理提供了IPAM控制器。

Deploy Citrix API Gateway Using OpenShift Operator 使用OpenShift Operator部署Citrix API Gateway

Perform the following steps to deploy the API gateway using the OpenShift Operator.

执行以下步骤以使用OpenShift Operator部署API网关。

1. In the OperatorHub, search for Citrix API Gateway Operator.
            在OperatorHub中，搜索Citrix API Gateway Operator。

2. Select the Citrix API Gateway Operator, and click Install.

2.选择Citrix API Gateway Operator，然后单击“安装”。

        OpenShift Operator Install
       
        OpenShift操作员安装
       

3. Choose the namespace where you want the operator to be installed and click Subscribe.

3.选择要在其中安装操作员的名称空间，然后单击“订阅”。

4. Once the Citrix API gateway operator is installed, you will see it listed under the Installed Operators section on the left panel. At this point, all CRDs are installed in the cluster.

4. Citrix API网关操作员安装完成后，您将在左侧面板的“ Installed Operators”部分中看到它的列出。 此时，所有CRD都已安装在群集中。

5. To create instances of each CRD, select the appropriate CRD, and click Create Instance.

5.要创建每个CRD的实例，请选择适当的CRD，然后单击创建实例 。

6. Once you create the instance you can see all your instances by selecting the All instances

6.创建实例后，您可以通过选择所有实例来查看所有实例

Update the CRD instance 更新CRD实例

To update any values of the created CRD instance, click on the instance, go to the YAML tab, edit the YAML file, and click Save.

要更新创建的CRD实例的任何值，请在该实例上单击，转到YAML选项卡，编辑YAML文件，然后单击Save 。

Delete the Instance and Operator 删除实例和运算符

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.

要删除CRD实例，您必须从用户界面中删除Citrix Ingress Controller实例。 选择实例右侧的三个垂直点，如下图所示，然后单击Delete CitrixIngressController 。

To delete the operator, click on the Actions drop-down list and then click Uninstall operator.

要删除操作员，请单击“ 操作”下拉列表，然后单击“ 卸载操作员” 。

Please note, you should delete all instances manually before uninstalling the operator. The instances are not automatically deleted if you uninstall the operator.

请注意，在卸载操作员之前，应手动删除所有实例。 如果卸载操作员，则不会自动删除实例。

Conclusion 结论

The Red Hat OpenShift Operator will ease the installation process of Citrix API gateway and enable all the required features to be configured on the go. Learn more about Citrix ADC and Citrix API gateway.

红帽OpenShift操作员将简化Citrix API网关的安装过程，并允许在旅途中配置所有必需的功能。 了解有关Citrix ADC和Citrix API网关的更多信息。

Originally published at https://www.citrix.com on August 27, 2020.

翻译自: https://medium.com/@tejaskonduri/deploy-citrix-api-gateway-using-red-hat-openshift-operator-citrix-blogs-996b48a4811b