- What's New
- Product Bulletin
- Service Overview
- Billing
- Getting Started
-
User Guide
- Application Service Mesh
- Buying a Service Mesh
- Mesh Management
- Service Management
- Gateway Management
- Grayscale Release
- Mesh Configuration
- Traffic Management
- Security
-
Best Practices
- Upgrading Data Plane Sidecars Without Service Interruption
- Service Governance for Dubbo-based Applications
- Reserving Source IP Address for Gateway Access
- Creating a Service Mesh with IPv4/IPv6 Dual Stack Enabled
- How Do I Query Application Metrics in AOM?
- Reducing the Agency Permissions of ASM Users
- Istio-ingressgateway HA Configuration
-
FAQs
- Service Mesh Cluster
-
Mesh Management
- Why Cannot I Create a Mesh for My Cluster?
- Why Are Exclusive Nodes Still Exist After Istio Is Uninstalled?
- How Do I Upgrade ICAgent?
- How Do I Enable Namespace Injection for a Cluster?
- How Do I Disable Sidecar Injection for Workloads?
- What Can I Do If A Pod Cannot Be Started Due to Unready Sidecar
- How Do I Handle a Canary Upgrade Failure?
-
Adding a Service
- What Do I Do If an Added Gateway Does Not Take Effect?
- Why Does It Take a Long Time to Start the Demo Application in Experiencing Service Mesh in One Click?
- Why Cannot I Access the page of the Demo Application After It Is Successfully Deployed?
- Why Cannot I Select the Corresponding Service When Adding a Route?
- How Do I Inject a Sidecar for the Pod Created Using a Job or CronJob?
- Performing Grayscale Release
-
Managing Traffic
- Why Are the Created Clusters, Namespaces, and Applications Not Displayed on the Traffic Management Page?
- How Do I Change the Resource Requests of the istio-proxy Container?
- Does ASM Support HTTP/1.0?
- How Can I Block Access from Some IP Address Ranges or Ports for a Service Mesh?
- How Do I Configure max_concurrent_streams for a Gateway?
- How Do I Fix Compatibility Issues Between Istio CNI and Init Containers?
-
Monitoring Traffic
- Why Cannot I View Traffic Monitoring Data Immediately After a Pod Is Started?
- Why Are the Latency Statistics on the Dashboard Page Inaccurate?
- Why Is the Traffic Ratio Inconsistent with That in the Traffic Monitoring Chart?
- Why Can't I Find Certain Error Requests in Tracing?
- Why Cannot I Find My Service in the Traffic Monitoring Topology?
- How Do I Connect a Service Mesh to Jaeger or Zipkin for Viewing Traces?
- Videos
-
More Documents
-
User Guide (ME-Abu Dhabi Region)
- Service Overview
- Getting Started
- User Guide
-
FAQs
- Service Mesh Cluster
- Mesh Management
-
Adding a Service
- What Do I Do If an Added Gateway Does Not Take Effect?
- Why Does It Take a Long Time to Start the Demo Application in Experiencing Service Mesh in One Click?
- Why Cannot I Access the page of the Demo Application After It Is Successfully Deployed?
- Why Cannot I Select the Corresponding Service When Adding a Route?
- Performing Grayscale Release
-
User Guide (ME-Abu Dhabi Region)
- General Reference
Show all
Copied.
Service Affinity
If node affinity is configured, the load balancer may fail to be accessed in some scenarios. For details, see Why the ELB Address Cannot Be used to Access Workloads in a Cluster?
- Log in to the CCE Console console and click the cluster name to access the cluster console. In the navigation pane, choose Services & Ingresses > Services. Then, locate the Service you want to operate and choose More > Edit YAML in the Operation column.
- Configure the following parameters in YAML:
spec: type: LoadBalancer externalTrafficPolicy: Local allocateLoadBalancerNodePorts: true
You can also choose More > Update in the Operation column of the Service to configure the parameters.
Parameter description
Parameter
Description
Service Affinity (externalTrafficPolicy)
The options are as follows:
Cluster-level (Cluster in YAML): Requests are forwarded within the cluster. The backend workload can be accessed from any node IP address and service port. However, routing hops bring in performance loss, and the client source IP address cannot be obtained.
Node-level (Local in YAML): Requests are forwarded only to the pod on the local node. If there is no pod, the requests will be suspended.
If dedicated load balancers are deployed for CCE Turbo clusters, passthrough networking is supported to reduce the network latency and ensure zero performance loss. In this case, the value must be Cluster-level (Cluster in YAML).
In other scenarios, requests are transmitted through a load balancer to a node and then forwarded to the target pod through the Service. In this case, the recommended value is Node-level (Local in YAML). The traffic is finally forwarded to the pod on the local node instead of being balanced to pods on other nodes. This avoids request exceptions caused by cross-node network faults.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot