configuring-service-meshes

Configure this skill configures service meshes like istio and linkerd for microservices. it generates production-ready configurations, implements best practices, and ensures a security-first approach. use this skill when the user asks to "configure service ... Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.

الانتقال إلى التثبيت

المستودع: jeremylongshore/tons-of-skills-marketplace
آخر نشاط في المصدر: ١٩ أغسطس ٢٠٢٦ في ١٢:١٣
لغة SKILL.md المكتشفة: الإنجليزية
النجوم: ٢٬٦٧٧
التفرعات: ٣٩٢

خيارات التثبيت

يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.

التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.

يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.

npx skills add https://github.com/jeremylongshore/tons-of-skills-marketplace --skill configuring-service-meshes

يبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.

تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.

مراجعة ملفات المصدر

اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.

مستكشف الملفات

12 ملفات

SKILL.md

تعليمات المصدر · معاينة للقراءة فقط

العودة إلى البحث العودة إلى التثبيت

Configuring Service Meshes

Overview

Configure service meshes (Istio, Linkerd, Consul Connect) for Kubernetes microservices architectures. Generate mTLS configurations, traffic management rules (routing, splitting, mirroring), observability integrations (distributed tracing, metrics), and resilience patterns (retries, circuit breakers, timeouts).

Prerequisites

Kubernetes cluster accessible via kubectl with admin permissions

Service mesh CLI installed: istioctl, linkerd, or consul

Helm 3+ for service mesh installation charts

Understanding of microservice communication patterns and dependencies

Observability backend available (Jaeger, Zipkin, or Prometheus/Grafana) for tracing and metrics

Instructions

Select the service mesh based on requirements: Istio for full-featured L7 control, Linkerd for lightweight simplicity, Consul Connect for multi-platform

Install the control plane: istioctl install --set profile=production or linkerd install | kubectl apply -f -

Enable sidecar injection for target namespaces: label namespaces with istio-injection=enabled or linkerd.io/inject=enabled

Configure mTLS: set PeerAuthentication to STRICT mode for zero-trust inter-service communication

Define traffic management rules: VirtualService for routing, DestinationRule for load balancing and circuit breaking

Set up traffic splitting for canary deployments: route a percentage of traffic to the new version

Configure retry policies and timeouts to improve resilience against transient failures

Integrate observability: connect to Jaeger/Zipkin for distributed tracing, Prometheus for metrics, and Kiali for visualization

Validate the mesh: verify sidecar injection, mTLS status, and traffic routing with istioctl analyze or linkerd check

Output

Service mesh installation manifests or Helm values

PeerAuthentication and AuthorizationPolicy manifests for mTLS and RBAC

VirtualService and DestinationRule manifests for traffic management

ServiceEntry manifests for external service access

Observability integration configuration (Jaeger, Prometheus, Kiali)

Error Handling

Error

Cause

Solution

sidecar not injected

Namespace not labeled for injection or pod has annotation to skip

Add istio-injection=enabled label to namespace; check pod annotations

mTLS handshake failed

Mismatched TLS settings between services or missing certificates

Set PeerAuthentication to PERMISSIVE temporarily; check istioctl proxy-status

503 Service Unavailable

Circuit breaker tripped or upstream connection pool exhausted

Review DestinationRule connection pool settings; increase maxConnections and http2MaxRequests

traffic not splitting correctly

VirtualService weight percentages misconfigured

Verify weights sum to 100; check VirtualService is bound to the correct gateway/host

high latency after mesh install

Sidecar proxy adding overhead or misconfigured timeouts

Tune proxy resources; review timeout settings; check if services are using HTTP/2

Examples

"Install Istio with strict mTLS on a production cluster and configure a VirtualService for canary routing: 90% to v1, 10% to v2."

"Set up Linkerd on a microservices cluster with automatic retries (3 attempts, 500ms timeout) and integrate with Prometheus for golden signal metrics."

"Configure an Istio AuthorizationPolicy that allows only the frontend service to call the API gateway, blocking all other inter-service traffic."

Resources

name	configuring-service-meshes
description	Configure this skill configures service meshes like istio and linkerd for microservices. it generates production-ready configurations, implements best practices, and ensures a security-first approach. use this skill when the user asks to "configure service ... Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.
allowed-tools	Read, Write, Edit, Grep, Glob, Bash(cmd:*)
version	1.24.0
author	Jeremy Longshore <jeremy@intentsolutions.io>
license	MIT
tags	["devops","security","microservices"]
compatibility

name	configuring-service-meshes
description	Configure this skill configures service meshes like istio and linkerd for microservices. it generates production-ready configurations, implements best practices, and ensures a security-first approach. use this skill when the user asks to "configure service ... Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.
allowed-tools	Read, Write, Edit, Grep, Glob, Bash(cmd:*)
version	1.24.0
author	Jeremy Longshore <jeremy@intentsolutions.io>
license	MIT
tags	["devops","security","microservices"]
compatibility

configuring-service-meshes

معلومات المصدر

خيارات التثبيت

مراجعة ملفات المصدر

المزيد من هذا المستودع

المزيد من هذا المستودع