Agent Plugins Marketplace
← All plugins

targetgroupbinding-unattached-tg-readiness-wedge

v1.0.0

Diagnose and unwedge Kubernetes rollouts stuck because an AWS Load Balancer Controller TargetGroupBinding points at a target group no listener rule forwards to. Use when: (1) `helm upgrade` / a Deployment rollout times out with "context deadline exceeded" while every container in the new pods is healthy, (2) new pods show `Ready=False` with reason `ReadinessGatesNotReady` and a readiness gate named `target-health.elbv2.k8s.aws/<name>`, (3) `aws elbv2 describe-target-health` shows every target `unused` / `Target.NotInUse`, (4) a PodDisruptionBudget reports `ALLOWED DISRUPTIONS: 0` and node drains or consolidation (e.g. Karpenter) are blocked by a service that serves no traffic, (5) you staged a target group ahead of its listener rule "so it's ready for the cutover" and want to know why that wedges every future rollout. Core facts: the controller injects a target-health readiness gate into every pod a TargetGroupBinding matches; a target group attached to no load balancer listener keeps its targets permanently `Target.NotInUse`, so the gate can never pass. Unwedge with `kubectl delete targetgroupbinding`; durable fix is gating the binding separately from the target group and attaching the listener rule before the binding.

Claude Code

By voitta-aiLicense: MIT3 GitHub starsUpdated 2 hours ago

Directory evidence

Runtimes
Claude Code
Parsed components
0 skill or MCP entries
Source updated
Sep 28, 2026
Manifest status
Canonical path parsed

The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →

Install targetgroupbinding-unattached-tg-readiness-wedge for Claude Code

Installs for the current user
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install targetgroupbinding-unattached-tg-readiness-wedge@agent-plugin-marketplace

Paste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.

The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.

Get the source manually
git clone https://github.com/voitta-ai/skillz

Clone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/targetgroupbinding-unattached-tg-readiness-wedge/.

Plugin files

plugins/targetgroupbinding-unattached-tg-readiness-wedge/
└── .claude-plugin/plugin.json

Plugin manifests1

plugins/targetgroupbinding-unattached-tg-readiness-wedge/.claude-plugin/plugin.json
{
  "name": "targetgroupbinding-unattached-tg-readiness-wedge",
  "description": "Diagnose and unwedge Kubernetes rollouts stuck because an AWS Load Balancer Controller TargetGroupBinding points at a target group no listener rule forwards to. Use when: (1) `helm upgrade` / a Deployment rollout times out with \"context deadline exceeded\" while every container in the new pods is healthy, (2) new pods show `Ready=False` with reason `ReadinessGatesNotReady` and a readiness gate named `target-health.elbv2.k8s.aws/<name>`, (3) `aws elbv2 describe-target-health` shows every target `unused` / `Target.NotInUse`, (4) a PodDisruptionBudget reports `ALLOWED DISRUPTIONS: 0` and node drains or consolidation (e.g. Karpenter) are blocked by a service that serves no traffic, (5) you staged a target group ahead of its listener rule \"so it's ready for the cutover\" and want to know why that wedges every future rollout. Core facts: the controller injects a target-health readiness gate into every pod a TargetGroupBinding matches; a target group attached to no load balancer listener keeps its targets permanently `Target.NotInUse`, so the gate can never pass. Unwedge with `kubectl delete targetgroupbinding`; durable fix is gating the binding separately from the target group and attaching the listener rule before the binding.",
  "version": "1.0.0",
  "author": {
    "name": "voitta-ai"
  },
  "homepage": "https://github.com/voitta-ai/skillz",
  "repository": "https://github.com/voitta-ai/skillz",
  "license": "MIT",
  "skills": "./skills/"
}

For maintainers

If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.

[targetgroupbinding-unattached-tg-readiness-wedge on Agent Plugins Marketplace](https://pluginsmp.com/plugins/targetgroupbinding-unattached-tg-readiness-wedge)