17 skills · sorted by relevance
Design traffic controls for AI inference services using Istio configuration examples. Covers mutual authentication, model version routing, gradual releases, retry limits, failure containment, and monitoring, with guidance for validating changes on the target cluster.
Set up monitoring for communication between services in Istio or Linkerd environments. Combine metrics, logs, and distributed traces, which follow requests across services, to investigate delays and errors, visualize dependencies, and define service quality targets.
Implement comprehensive observability for service meshes including distributed tracing, metrics, and visualization. Use when setting up mesh monitoring, debugging latency issues, or implementing SLOs for service communication.
The English summary is being prepared. Showing the original description.
Design service meshes with Istio or Linkerd, including traffic management, security, and observability. Use when configuring service communication, mesh policies, or multi-cluster networking.
The English summary is being prepared. Showing the original description.
Implement Istio and Linkerd service meshes. Configure mTLS, traffic management, and observability. Use when managing microservices communication.
The English summary is being prepared. Showing the original description.
Use service mesh patterns for AI inference traffic management, mTLS, canary releases, policy enforcement, and cross-cluster resilience.
The English summary is being prepared. Showing the original description.
Manage Istio service mesh for traffic management, security, and observability. Use for traffic shifting, canary releases, mTLS, and service mesh troubleshooting.
The English summary is being prepared. Showing the original description.
Implement production-ready service mesh deployments with Istio, Linkerd, or Cilium. Configure mTLS, authorization policies, traffic routing, and progressive delivery patterns for secure, observable microservices. Use when setting up service-to-service communication, implementing zero-trust security, or enabling canary deployments.
The English summary is being prepared. Showing the original description.
Use service mesh patterns for AI inference traffic management, mTLS, canary releases, policy enforcement, and cross-cluster resilience.
The English summary is being prepared. Showing the original description.
Configures Envoy, the high-performance C++ edge and service proxy, as an API gateway, load balancer or service mesh sidecar with L4/L7 routing, retries, circuit breaking, rate limiting, TLS and observability. Use when a user asks to set up Envoy, write an envoy.yaml, route traffic to backends, add health checks or rate limits, do a canary split, read Envoy admin stats, or understand the proxy behind Istio and Envoy Gateway.
The English summary is being prepared. Showing the original description.
HashiCorp Consul for service discovery, health checking, and service mesh. Use when the user needs to register services, perform health checks, store configuration in the KV store, or set up Connect for secure service-to-service communication.
The English summary is being prepared. Showing the original description.
Design service mesh observability — distributed tracing, service-level metrics, and dashboards. Use when asked to "add service mesh observability", "set up distributed tracing in the mesh", or "build service-level dashboards".
The English summary is being prepared. Showing the original description.
Design a service mesh deployment — technology selection, mTLS policy, and traffic management config. Use when asked "should we use a service mesh", "Istio or Linkerd", or "design our mTLS policy".
The English summary is being prepared. Showing the original description.
Audit existing service mesh configuration — find mTLS gaps, traffic policy issues, and observability holes. Use when asked to "audit our service mesh", "find mTLS gaps", or "review traffic policy issues".
The English summary is being prepared. Showing the original description.
API gateway and reverse proxy configuration with Kong, Nginx, Traefik, routing, and auth middleware. Activate on: API gateway, reverse proxy, Kong, Nginx, Traefik, load balancer, ingress, auth middleware. NOT for: rate limiting algorithms (use api-rate-limiting-throttling-expert), service mesh (use service-mesh-microservices-expert).
The English summary is being prepared. Showing the original description.
Use verified service mesh patterns for AI inference traffic management, mTLS, canary releases, policy enforcement, and cross-cluster resilience.
The English summary is being prepared. Showing the original description.
API gateway and reverse proxy configuration with Kong, Nginx, Traefik, routing, and auth middleware. Activate on: API gateway, reverse proxy, Kong, Nginx, Traefik, load balancer, ingress, auth middleware. NOT for: rate limiting algorithms (use api-rate-limiting-throttling-expert), service mesh (use service-mesh-microservices-expert).
The English summary is being prepared. Showing the original description.