Catalog Details
CATEGORY
traffic-managementCREATED BY
UPDATED AT
May 17, 2024VERSION
1.0
Pattern Snapshot
Related Patterns
Install-Traefik-as-ingress-controller
MESHERY4796
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
- Apr 14 | Unable to deploy meshery to minikube
- May 08 | No reachable contexts found in the uploaded kube config
- May 08 | Meshery Development Meeting | May 8th 2024
- May 01 | WEBINAR: Making the CNCF Landscape interactive with Meshery
- Apr 24 | Meshery Development Meeting | April 24th 2024
- Mar 11 | [Help Wanted] A list of open DevOps-centric needs on Meshery projects
- Apr 16 | Help needed for setup of meshery cli
- Apr 17 | Meshery Development Meeting | April 17th 2024
- Apr 12 | What exactly is this sistent design system project
- Nov 11 | Unable setup local Meshery development server