You can create a cloud-native gateway for TKE, associate services from a registry or TKE, and then create routing policies for the services within the gateway, enabling them to be exposed through the gateway. This guide uses TKE as an example. You need to complete the following steps:
Currently, Cloud Native Gateway only supports adding user accounts to the purchase allowlist in microservice scenarios, where it serves as the service access layer for Polaris (Polaris). New access is not supported in other scenarios. When the console is accessed in non-supported scenarios, users will be redirected to the Polaris (Polaris) console.
Experience process
If microservices are deployed to TKE, the Cloud Native Gateway can directly associate services from TKE.
1. Click the ID of the created cloud-native gateway to go to the Basic Information page.
2. In the left menu bar, choose Service Routing > Service Source. In the service source list, click Create. For service source type, select TKE. For the service instance, select an available instance that resides in the same VPC as the cloud-native gateway. Click Submit.
Step 3: Adding a Service
1. Select Service Routing > Service, click Create in the service list, select K8S service for service type, and choose the associated service source from the previous step. Fill in the namespace name and service name of the container service.
2. Click Submit. After creation, you can view the service information in the service list.
Step 4: Configuring Routing Rules for the Service
1. After the backend service is added, click the service name to enter the Service & Route > Route page.
2. Click Create, set the routing information, and click Next.
Remarks:
At least one of Request Method, Request Path, and Host needs to be configured.
3. Configure the backend service information of the route. After you confirm that the backend service information is correct, click Confirm to complete route creation.
Step 5: Accessing the Route
1. Go to the Basic Information page of the cloud-native gateway and obtain the CLB address.
2. Use the CLB address and the configured route path to access the API. Execute a curl command to test, confirming that TKE is successfully accessed through the cloud-native gateway.
