Aspect | Description |
---|---|
Failure Detection | Identify if a service is no longer responding or experiencing difficulties using various methods like heartbeats, ping requests, or error rates |
Circuit Opening and Closing | When a failure is detected, open a "circuit" to divert traffic away from the affected service. Close the circuit when the issue is resolved, restoring traffic to the original service |
Fallback Strategies | Define actions to take when a circuit break occurs, e.g., retry the request, send it to a backup service, or return an error |
Aspect | Description |
---|---|
Round Robin | Distribute incoming requests equally across all available instances |
Least Requests | Send incoming requests to the instance with the fewest active requests |
IP Hash | Use a hash function to map incoming requests to specific instances |
Session Persistence | Ensure that subsequent requests from the same client are always routed to the same instance |
Aspect | Description |
---|---|
Proxying | Acts as a proxy between the client and the service, allowing for interception of incoming requests and outgoing responses |
Route Configuration | Allows developers to configure routes within the service mesh to control how requests are handled |
Path Based Routing | Enables developers to route requests based on the URL path, allowing them to create and manage API versions or route requests to different backend services |
Query Parameter Based Routing | Allows develop |
| Tool | Layer of Operation | Traffic Management | Caching and Compression | Security | Visibility and Monitoring | Scalability | Complexity | | ------------------------- | --------------------- | ----------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------ | ---------------
Aspect | Description |
---|---|
Isolate Namespaces, Pods, and Services | Use network policies to block all incoming and outgoing traffic by default, and then create additional policies to allow specific types of traffic |
Enforce Security Policies | Create network policies that follow organizational security standards or comply with regulatory requirements |
Implement Micro-Segmentation and Zero Trust Networking | Use network policies to restrict com |
| Network Model | Isolation | Complexity | Scalability | Security | Performance | Protocols | Control | Encapsulation | Flow | Advantages | Disadvantages | Use Cases
Network Model | Description |
---|---|
Amazon Elastic Container Service for Kubernetes (EKS) | Offers a highly scalable and secure network fabric for Kubernetes by leveraging Linux kernel modules and SDN technologies |
Antrea | Implements a highly scalable and secure network fabric for Kubernetes using Linux kernel modules and iptables rules |
Aqua | Offers a highly scalable and secure network fabric for Kubernetes through the utilization of Linux ker |
Service | Use Case |
---|---|
ClusterIP | Suitable for intra-cluster communication between components within a multi-tier application. For example, a web server and database server might communicate via a ClusterIP service |
NodePort | Ideal for exposing applications to external clients or services, such as a customer-facing web portal or API gateway |
LoadBalancer | Well-suited for high-traffic applications requiring load balancing and scaling capabilities, such as a large e-commerce website or mobile app |
ExternalName | Useful |
Tool | Description |
---|
Pros | Cons |
---|---|
Stable and predictab |