Catalog Details

• CATEGORY

  traffic-management

• CREATED BY

  Deepak Reddy

• UPDATED AT

  January 02, 2025

• VERSION

  0.0.1

Pattern Snapshot

Related Patterns

traffic-management

Understanding the difference between Edge Relationships

MESHERY4f72

What this pattern does:

Service Internal Traffic Policy enables internal traffic restrictions to only route internal traffic to endpoints within the node the traffic originated from. The "internal" traffic here refers to traffic originated from Pods in the current cluster. This can help to reduce costs and improve performance. How it works ?? The kube-proxy filters the endpoints it routes to based on the spec.internalTrafficPolicy setting. When it's set to Local, only node local endpoints are considered. When it's Cluster (the default), or is not set, Kubernetes considers all endpoints.

Caveats and Consideration:

Note: For pods on nodes with no endpoints for a given Service, the Service behaves as if it has zero endpoints (for Pods on this node) even if the service does have endpoints on other nodes.

Compatibility:

Recent Discussions with "meshery" Tag

• Dec 31 | 404 page not found Anuj Kumar Sharma
• Dec 30 | Seeking Help with Playground Features for Complex Designs Appareddy Dwarampudi
• Dec 04 | Link Meshery Integrations and Github workflow or local code Shlok Mishra
• Nov 25 | Issue: Unable to Run make server-local in Meshery Cloud Setup Due to Soda CLI Dependency Md Kaif Ansari
• Nov 28 | Issue on Setting Up Meshery Using Docker Kean Serna
• Nov 22 | Meshery CI Maintainer: Sangram Rath Vivek Vishal
• Nov 25 | T.roles_names is undefined ( permission path is not provided ) Shlok Mishra
• Nov 20 | Meshery Development Meeting | Nov 20th 2024 Vivek Vishal
• Nov 10 | Error in "make server" and "make ui-server" Aadarsh Shekhar
• Nov 11 | Difference in dev Environments on port 9081 and 3000 Divyansh Khatri