agentleFS
Sign inStart free
nitinjain999nitinjain999/platform-skills/skills/progressive-delivery/SKILL.md

progressive-delivery

Skill71 starsChanged 8 days agoApache-2.0View on GitHub

Canary releases with automatic promotion and rollback using Flagger on Flux. Shifts traffic through Gateway API HTTPRoute weights (Envoy Gateway for north-south, Linkerd for east-west), gates each step on success-rate and latency metrics for the canary pods, runs smoke tests before traffic moves, and rolls back on its own when checks fail. Covers install with signed OCI charts, Canary and MetricTemplate design, GitOps ownership, and emergency rollback. Use when asked to "add canary deployments", "roll out gradually", "automatic rollback on errors", "set up Flagger", or "why did my canary roll back". Gateway and routes themselves → /platform-skills:gateway-api. Linkerd mesh issues → /platform-skills:linkerd.

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 2 are distinctive, and 5 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 5

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read references/progressive-delivery.md before responding.

    line 12
  2. Very specific:

    Start from examples/progressive-delivery/app/canary.yaml.

    line 28
  3. Very specific:

    Add autoscalerRef when the app has an HPA.

    line 29
  4. Very specific:

    If the Canary has webhooks, include examples/progressive-delivery/app/loadtester.yaml in the app namespace.

    line 31
  5. Very specific:

    Remove the app's hand-written HTTPRoute in the same change.

    line 32
  6. Distinctive:

    Use the reference's rollback table.

    line 37
  7. Distinctive:

    Every mode ends with:

    line 41

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Ship a new version to a slice of real traffic first, promote it only on evidence, and roll it back without a human when the evidence says no.

Read references/progressive-delivery.md before responding. It holds how a Flagger analysis runs, the provider settings for Envoy Gateway and Linkerd, metric rules, GitOps ownership, rollback by situation, and troubleshooting. The working manifests are in examples/progressive-delivery.

This skill is interactive by default. With no arguments, ask how traffic reaches the app (shared Envoy Gateway, Linkerd east-west, both), where metrics come from (Linkerd viz, gateway Prometheus, other), and whether the app has an HPA, then run canary. Never apply resources or change a live Canary yourself.

Mode dispatch

ModeWhat it does
installFlagger via Flux from the signed OCI chart, with meshProvider and metricsServer for the user's traffic and metrics
canaryCanary and MetricTemplates for one app, from examples/progressive-delivery, adapted to its ports, hostname, listener and HPA
metricsDesign or fix the MetricTemplate queries so they measure the canary pods only, and prove they return data
debugWhy a canary is stuck, never starts, or always rolls back, from Flagger events and route status
rollbackThe right rollback for the situation: automatic, revert in Git, skipAnalysis, or suspend

Mode: canary

  1. Start from examples/progressive-delivery/app/canary.yaml. Set targetRef, service.port and targetPort, hosts, and gatewayRefs (the Gateway and sectionName for north-south; the Service for Linkerd east-west).
  2. Add autoscalerRef when the app has an HPA.
  3. Pick interval, stepWeight, maxWeight and threshold from the app's traffic: a check needs enough requests per interval to be meaningful; a low-traffic app needs a load-test webhook or a longer interval.
  4. If the Canary has webhooks, include examples/progressive-delivery/app/loadtester.yaml in the app namespace; the webhook URL must name that Service.
  5. Remove the app's hand-written HTTPRoute in the same change; say so explicitly.
  6. Validate with kubeconform -strict against the CRD catalog, as the example README shows.

Mode: rollback

Use the reference's rollback table. State which objects Flagger owns (primary, generated Services and HTTPRoute) and that the fix for a failed release is always a change in Git, because Flux will keep applying whatever Git says.

Output format

Every mode ends with:

  • Changes, as exact files and fields
  • Blast radius, in one line (which traffic and for how long)
  • Validation, as commands (kubectl describe canary, the metric query, route status)
  • Rollback, for the situation in question

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free