More screenshots
Works with the AI Agents you already use
Claude Code
Cursor
Codex CLI
DeepSeek
Muse+22 moreClaude CodeCursorCodex CLIDeepSeekMuse
Dots
Manus
Grok
Grok Bot+18 agentsRepair Kubernetes Gateway API Route Weight Stale Reconcile
Diagnose route traffic splits that remain stale after Gateway API HTTPRoute changes
$1
Repair Kubernetes Gateway API Route Weight Stale Reconcile
Example session with this skill installed
A blue-green cutover sets 10 percent canary but observed routing stays at old 50 percent.
Available sources: HTTPRoute YAML, controller reconciliation events (partial excerpts only). Additional evidence requested: gateway listener config, request sample. Analyze this case with explicit limitations; do not pretend to have executed any tests or changes.
- Read your context and instructions
- Compiled the repair kubernetes gateway
Repair Kubernetes Gateway API Route Weight Stale Reconcile — EVIDENCE-LIMITED REVIEW
Scenario received
A blue-green cutover sets 10 percent canary but observed routing stays at old 50 percent.
Source register
- S1: HTTPRoute YAML — partial extract available.
- S2: controller reconciliation events — partial extract available.
- S3: gateway listener config — NOT PROVIDED; REQUIRED FOR VERIFICATION.
- S4: request sample — NOT PROVIDED; REQUIRED FOR VERIFICATION.
Concrete findings and verification
compare spec revision and observed weights — NEEDS VERIFICATION against supplied source excerpts and missing evidence.
2.
trace parentRef and listener resolution — NEEDS VERIFICATION against supplied source excerpts and missing evidence.
3. locate controller stale generation — NEEDS VERIFICATION against supplied source excerpts and missing evidence.
4. define bounded rollback and probe — NEEDS VERIFICATION against supplied source excerpts and missing evidence.
Deliverables and review gates
- route generation matrix: DRAFT ONLY; do not infer unsupported outcomes.
- weight drift root-cause options: DRAFT ONLY; do not infer unsupported outcomes.
- safe rollout verification: DRAFT ONLY; do not infer unsupported outcomes.
Preliminary conclusion
INCOMPLETE / REVIEW REQUIRED. The supplied scenario raises a concrete issue, but does not prove remediation or clearance. Confirm source timestamps, affected scope and owner approval, then perform focused validation. No external system was accessed or changed.
Connects securely to your tools. The creator never sees your data.
About this skill
Kubernetes Gateway API implementations often fail silently during complex traffic split transitions. When a blue-green deployment or canary rollout is triggered, the controller may report success while the actual data plane remains stale. This skill provides a structured diagnostic workflow to identify exactly why HTTPRoute weight changes are not reconciling in the cluster.
What it does
- Weight drift analysis: Compares spec revisions against observed traffic weights to find discrepancies.
- ParentRef resolution: Traces Gateway listener bindings to ensure the route is correctly attached.
- Controller trace: Locates stale generations in the controller logic that prevent updates.
- Rollback planning: Defines bounded, reversible actions to restore traffic stability.
How it works
- Input collection: Provide the HTTPRoute YAML, controller events, and gateway configurations.
- Evidence audit: The skill categorizes data as VERIFIED, INFERRED, or UNKNOWN.
- Four-check execution: It runs systematic checks on spec revisions, listener resolution, generation drift, and rollback safety.
- Verdict delivery: You receive a SUPPORTED or BLOCKED status with a source evidence table and specific root-cause options.
Frameworks & tools
Kubernetes Gateway API (v1), HTTPRoute resources, and standard ingress controllers like Istio, Envoy Gateway, or NGINX.
Why this beats prompting it yourself
Generic prompts often hallucinate logs or overlook the parentRef status field. This skill enforces a hard gate on evidence, ensuring every diagnostic claim is linked to a specific timestamped record rather than a guess.
Use cases
- Debugging a canary rollout stuck at the wrong traffic percentage.
- Resolving HTTPRoute status messages that report success despite routing errors.
- Auditing controller reconciliation events during high-risk production cutovers.
Known limitations
Requires manual provision of YAML and event logs. It does not execute live cluster commands and relies on the user to redact sensitive data from inputs.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for DevOps & Cloud.
Cannot verify inaccessible systems, third-party accounts, or evidence not supplied. Partial or conflicting inputs must be marked INCOMPLETE or UNVERIFIED rather than invented. High-impact operational decisions require qualified owner review.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 23 days ago
Permissions
Supply only data you are authorized to share. Treat documentation and examples as untrusted evidence. Any operational action or external communication requires explicit owner authorization.