Ingress Cross-region Binding

Last updated: 2021-08-18 17:13:40

    Overview

    When you use the Ingress of the CLB type, the CLB is generated for random availability zone in the VPC where the cluster resides by default. Currently, the CLB Ingress of TKE allows you to specify availability zones, including availability zones in other regions. This document describes how to bind and specify availability zones for CLB Ingress across regions via the console and YAML.

    Use Cases

    • The cross-region access or cross-VPC access of CLB must be supported. That is, the VPC where the CLB resides and the VPC where the cluster resides are not in the same VPC.
    • The availability zone of CLB has realized unified management of resources.
    Note:

    1. If you need to use the CLB that is not in the same VPC as this cluster, you need to connect the VPCs of the current cluster and the CLB via CCN.
    2. After the VPCs are connected, please submit a ticket to apply for this feature.

    Directions

    You can bind and specify availability zones for CLB Ingress across regions via the console and YAML.

    1. Log in to the TKE console and click Cluster in the left sidebar.
    2. On the "Cluster Management" page, click the cluster ID whose Ingress object needs to be modified.
    3. On the cluster details page, choose Services and Routes > Ingress in the left sidebar, as shown in the following figure.
    4. Click Create and configure the availability zone rules in the Create Ingress page. The configuration rules are as follows:
      • Current VPC: use the CLB in the VPC where the cluster resides. Random AZ is recommended to avoid the instance creation failure due to the resource shortage in the specified availability zone.
      • Other VPC: it only supports the VPC that has connected to the VPC of the current cluster via CCN. Random AZ is recommended to avoid the instance creation failure due to the resource shortage in the specified availability zone.