This topic describes how to add services, manage services, manage service versions, manage service traffic rules, and configure active health checks for services in a cloud-native gateway. This helps you efficiently optimize service management and improves system performance and reliability.
Add a service
Cloud-native gateways allow you to add services from the following sources: Container Service for Kubernetes (ACK) clusters, Microservices Engine (MSE) Nacos instances, fixed endpoints, Domain Name System (DNS) domain names, and Function Compute. To allow a gateway to obtain service endpoints, you must add an existing service to the gateway and register the service as a destination service for routing in the console. For more information, see Add a service.
Manage services
After you add a service whose Service Source is set to Fixed Address to a gateway, the endpoint of the backend node that corresponds to the service may change. If the service is not registered with the service source of the gateway, the gateway cannot dynamically obtain the new endpoint of the backend node. In this case, to allow the gateway to obtain the new endpoint, you must modify the service information to manually adjust the endpoint of the backend node that corresponds to the service. For more information about how to view, edit, and delete a service, see Manage services.
Manage service versions
Service versions are used for the tag-based routing feature that is configured for routes of a cloud-native gateway. You can configure tag-based routing policies for routes to meet requirements in scenarios such as canary releases, tag-based routing, and high-availability deployments. For more information about how to add, edit, and delete a service version, see Manage service versions.
Manage service traffic rules
You can configure traffic rules to control the process of how traffic is transferred from the gateway to the backend service. The rule configuration includes the encryption type and load balancing policy. This ensures secure and efficient traffic transfer from the gateway to the backend service. You can manage the following items:
Encryption configurations of backend service certificates.
Load balancing policies of backend services.
For more information, see Manage traffic rules.
Configure active health checks for services
After you configure the active health check feature for services, the system automatically deactivates unhealthy nodes based on the health check result. The system also automatically activates nodes if the nodes are restored to a healthy state. The active health check feature helps improve the availability of routes to the service interface when multi-replica deployment is used for your backend services.
Configure active health checks for services.
Troubleshoot health check failures.
For more information, see Configure active health check for services.