DevOps & Infra Skill
Bash Defensive Patterns
Master defensive Bash programming techniques for production-grade scripts.
$15
Istio Traffic Management
Configure Istio traffic management including routing, load balancing, circuit breakers, and…
A comprehensive guide to Istio traffic management for production service meshes, covering routing, load balancing, circuit breakers, and progressive delivery. It ships ready-to-apply VirtualService and DestinationRule templates for canary releases, retries, traffic mirroring, fault injection, and ingress gateways.
$15 one-time
Add to a kit → Prices include 20% VAT. · Forged on real agency work · one-time, no lock-in
- Type Skill
- Category DevOps & Infra
- Delivery Email · instant
- License One-time
Inside the run · no black box
See the actual work before you buy it.
On a mesh, resilience is configuration rather than code. Routing skeletons come first, canaries shift by weight against hard metric gates, and faults get injected on purpose before production injects them for you.
- Defines the routing skeleton first: VirtualService for host-based routing decisions, DestinationRule subsets (v1, v2, stable, canary) mapped to pod version labels, so every later policy has named targets.
- Rolls canaries by weight: stable 90, canary 10, watched against explicit gates (error rate under 0.1 percent, p99 under 500ms), then raised stepwise toward 100; if metrics degrade the weight snaps back to zero immediately.
- Installs resilience as configuration, not code: outlierDetection ejects a pod after 5 consecutive 5xx errors with capped ejection percent so the service never fully self-amputates, plus connection pools, retries with per-try timeouts and a retryOn list.
- Mirrors production traffic to the next version: a full shadow copy whose responses are discarded, used for load testing and regression hunting with zero user impact, with the hard rule that mirrored traffic must never write to production state.
- Injects faults on purpose: fixed delays and 503 aborts at controlled percentages to prove that client timeouts, circuit breakers and graceful degradation actually fire before a real incident tests them.
- Debugs from the proxy's point of view: istioctl analyze for config sanity, then proxy-config routes and endpoints to see what Envoy is really doing rather than what the YAML claims.
One power source. 6 lines out.
istio-traffic-management · core
core active · 6 lines
- ✓ configuring service-to-s…
Configuring service-to-service routing with header and weight-based rules
- ✓ running canary or blue-g…
Running canary or blue-green deployments with percentage-based traffic shifting
- ✓ setting up circuit break…
Setting up circuit breakers and outlier detection to prevent cascading failures
- ✓ mirroring production tra…
Mirroring production traffic to a test version for safe load testing
- ✓ injecting controlled fau…
Injecting controlled faults to validate retry and timeout resilience
- ✓ configuring ingress gate…
Configuring ingress gateways with TLS and path-based routing
Yours to keep.
Drag time forward. Watch what stays.
Forever
That's what owning means.
The rented stack
ai writing tool: subscription
expired · access lostanalytics suite: subscription
expired · access lostdesign platform: subscription
expired · access lost(nothing left)
Your forge
-
Ship new versions safely by testing with a small traffic slice before full rollout
license: perpetual -
Prevent one failing service from cascading into a cluster-wide outage
license: perpetual -
Test against real traffic with zero user risk using shadow mirroring
license: perpetual -
Manage all traffic policy declaratively without touching application code
license: perpetual
subscriptions expire · deeds don't
Everything in the box.
Pick a piece up. Watch it work.
Basic routing template with VirtualService and DestinationRule subsets
6 parts · one working system · ships instantly by email
This wasn't forged for everyone.
- Not for you if you'd rather rent a tool than own one.
- Not for you if you want someone else to run your stack.
- Not for you if you're happy guessing.
Platform and DevOps engineers running Kubernetes service meshes who need production-grade traffic control, resilience, and progressive delivery with Istio.
then this was forged for you.Works with
Universal by design: these run in any AI. Delivered in the open Agent Skills + MCP format (native in Claude); ChatGPT, Gemini, Cursor and Copilot adapt the same files their own way.
- Claude Native format
- ChatGPT Adapts via open standards
- Gemini Adapts via open standards
- Cursor Adapts via open standards
- Copilot Adapts via open standards
Catch what's on your mind.
the air is clear. nothing between you and the forge.
catch a spark: the forge will answer
-
We run Linkerd, not Istio. Do the templates transfer?
Not directly. Everything is built on Istio CRDs, VirtualService and DestinationRule, so the concepts like canary, circuit breaking, and mirroring carry over but the YAML doesn't. If you're not running Istio, you'll get limited value here.
-
How does a canary actually work without touching application code?
Traffic policy is fully declarative: a DestinationRule defines the new version as a subset, and a VirtualService routes a small percentage of traffic to it. You raise the weight gradually, and rolling back is a one-line weight change. istioctl commands let you verify the live routes at each step.
-
Does it install and operate Istio for me?
No. It assumes a running mesh; installation, upgrades, and mesh operations are out of scope. The value is the traffic-management layer: routing, resilience, mirroring, fault injection, and ingress templates ready to apply.
-
How is it delivered?
By email right after purchase: ready to run, downloaded instantly, no setup wait.
-
One-time or subscription?
A one-time purchase; no subscription or hidden fees. VAT (20%) is included.
-
Can I get a refund?
As a digital product, it can’t be refunded once downloaded. That’s why we show exactly what’s inside and who it’s for, right here.