Adding a Gateway

Prerequisites

Gateways use load balancers of ELB to provide network access. Before adding a gateway, you need to create a load balancer.

When creating a load balancer, you need to ensure that it belongs to the same VPC as the cluster. For details, see Creating a Shared Load Balancer.

Procedure

1. Log in to the ASM console and click the name of the target service mesh to go to its details page.
2. In the navigation pane on the left, choose Gateway Management and click Add Gateway.
3. Configure the following parameters.
   • Gateway Name

     Enter a gateway name. Enter 4 to 59 characters starting with a lowercase letter and ending with a lowercase letter or digit. Only lowercase letters, digits, and hyphens (-) are allowed.

   • Cluster

     Select the cluster to which the gateway belongs.

   • Access Mode
     • IP Version: The value can be IPv4 or DualStack. This parameter is available only when IPv6 is enabled.
     • Gateways use shared load balancers of ELB for the access over both public and private IPv4 networks.
   • Access Entry
     • External Protocol

       Select one to match the protocol type of your service. HTTP, gRPC, TCP, TLS, and HTTPS are supported.

     • External Port

       Enter the port number exposed in the Load Balancer Service address. The port number can be specified randomly.

     • External Access Address

       The system automatically fills in the IP address of the load balancer as the service access entry. You can also change the IP address to the domain name associated with the load balancer.

     • TLS Termination

       If External Protocol is HTTPS, TLS Termination is enabled and cannot be disabled.

       If External Protocol is TLS, you can enable or disable TLS Termination. If you enable TLS termination, bind a certificate to support TLS-based data transmission encryption and authentication. If you disable TLS termination, encrypted TLS data will be directly forwarded.

     • Secret Certificate
       • When configuring a TLS protocol with TLS termination enabled, you need to bind a certificate to support TLS-based data transmission encryption and authentication.
       • When configuring the HTTPS protocol, you need to bind a secret certificate.
     • Earliest TLS Version Supported/Latest TLS Version Supported

       When configuring a TLS protocol with TLS termination enabled or an HTTPS protocol, you can select the earliest and latest TLS versions.

   Figure 1 Adding a gateway
   

4. (Optional) Configure routing parameters.

   When the access address of a request matches the forwarding policy (which consists of an external access address and URL), the request is forwarded to the corresponding target Service for processing. Click . The Add Route dialog box is displayed.

   • URL Matching Rule
     • Prefix: A URL can be accessed if its prefix is the same as that you configure. For example, /healthz/v1 and /healthz/v2.
     • Exact: Only the URL that fully matches the values you set can be accessed. For example, if the URL is set to /healthz, only /healthz can be accessed.
   • URL

     Mapping URL supported by the service, for example, /example.

   • Namespace

     Select the namespace to which the gateway belongs.

   • Target Service

     Service of the gateway. Select a value from the drop-down list box. The target service is filtered based on the corresponding gateway protocol. For details about the filtering rules, see Why Cannot I Select the Corresponding Service When Adding a Route?

     The service which configuration diagnosis fails cannot be selected. You need to fix the issues first. For details, see Manual Fixing Items or Auto Fixing Items.

   • Access Port

     Only ports that match external protocols are displayed.

   • Rewrite

     (This parameter is configurable when the external protocol is HTTP.)

     Rewrite the HTTP URI and host/authority header before forwarding. Disabled by default. To enable it, configure the following parameters:

     • URI: This value is used to rewrite the URI or prefix.
     • Host/Authority Header: This value is used to rewrite the HTTP host/authority header.
   Figure 2 Adding a route
   

5. Click OK.

   You can obtain the external network access address of the service in the Service Management page.

   Figure 3 External network access address of the service