jeremylongshore/tons-of-skills-marketplace / plugins/devops/service-mesh-configurator/skills/configuring-service-meshes
configuring-service-meshes
VerifiedConfigure 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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 4.4 KB |
| assets/README.md | markdown | 496 B |
| assets/error_handling_strategies.md | markdown | 8.4 KB |
| assets/example_microservices_architecture.md | markdown | 5.5 KB |
| assets/istio_config_template.yaml | config | 2.3 KB |
| assets/linkerd_config_template.yaml | config | 3.5 KB |
| references/README.md | markdown | 68 B |
| scripts/README.md | markdown | 506 B |
| scripts/deploy_config.shexecutable | script | 7.6 KB |
| scripts/generate_test_traffic.pyexecutable | script | 14.3 KB |
| scripts/rollback_config.shexecutable | script | 8.2 KB |
| scripts/validate_config.pyexecutable | script | 9.7 KB |
assets/linkerd_config_template.yaml
View on GitHub# Linkerd Configuration Template
# This template provides a starting point for configuring Linkerd service mesh.
# Replace placeholders (example-value, YOUR_VALUE_HERE) with your actual values.
# ---
# Global Configuration
# ---
global:
# Namespace for Linkerd control plane components. Consider a dedicated namespace.
namespace: linkerd
# Cluster domain. Used for service discovery.
clusterDomain: cluster.local
# Enable tracing. Requires a tracing backend like Jaeger or Zipkin.
tracing:
enabled: false
# Endpoint for the tracing collector (e.g., Jaeger). Uncomment and configure if enabled.
# collectorEndpoint: http://jaeger.linkerd.svc.cluster.local:14268/api/traces
# Control plane version. Should match the Linkerd version.
controlPlaneVersion: example-value # Example: stable-2.14.3
# ---
# Namespace-Specific Configuration
# ---
namespaces:
- name: YOUR_NAMESPACE_HERE # The namespace where your microservices are deployed.
# Automatically inject Linkerd proxies into pods in this namespace.
autoInject: true
# Resources to be injected into the namespace. Optional.
resources:
# Limit ranges for resource consumption.
limitRanges:
- name: default-limits
spec:
limits:
- default:
cpu: "500m" # 0.5 CPU core
memory: "512Mi"
defaultRequest:
cpu: "100m" # 0.1 CPU core
memory: "128Mi"
type: Container
# Resource quotas for the namespace.
resourceQuotas:
- name: default-quota
spec:
hard:
pods: "10" # Maximum number of pods in the namespace
cpu: "5" # 5 CPU cores
memory: "5Gi"
# ---
# Workload-Specific Configuration (Example: Deployment)
# ---
workloads:
- kind: Deployment
name: YOUR_DEPLOYMENT_NAME_HERE # Name of your deployment
namespace: YOUR_NAMESPACE_HERE
spec:
# Configure proxy settings for the workload.
proxy:
# CPU and memory requests/limits for the proxy container. Adjust based on workload needs.
resources:
requests:
cpu: "50m"
memory: "64Mi"
limits:
cpu: "200m"
memory: "128Mi"
# Configure the proxy's outbound concurrency. Helps prevent overwhelming downstream services.
# outboundConcurrency: 100 # Example value
# Enable traffic shifting. Requires a traffic split resource.
trafficSplit:
enabled: false
# Set log level for the proxy. Useful for debugging.
logLevel: info # Options: debug, info, warn, error
# Enable Prometheus metrics scraping for this workload.
metrics:
enabled: true
# Enable retries for failed requests. Configure retry policies carefully.
retry:
enabled: false
# retryPolicy:
# numRetries: 3
# perTryTimeout: 1s
# ---
# Service-Specific Configuration (Example: Service)
# ---
services:
- name: YOUR_SERVICE_NAME_HERE # Name of your service
namespace: YOUR_NAMESPACE_HERE
spec:
# Configure service profile for the service.
serviceProfile:
enabled: true # Enables Linkerd to collect metrics and provide routing information
# Add routes for different endpoints. Example:
# routes:
# - name: /api/v1/users
# condition:
# method: GET
# pathRegex: /api/v1/users
# isRetryable: trueRelated skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |