From rmq-vertical-scaler
Use when an operator wants to install or deploy the rmq-vertical-scaler into a Kubernetes cluster — generating manifests from a config, ensuring the RabbitMQ credentials secret exists, applying with kubectl, and verifying the rollout.
How this skill is triggered — by the user, by Claude, or both
Slash command
/rmq-vertical-scaler:rmq-deployThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
One binary does two jobs: `generate` emits manifests locally; the same image runs `run` in-cluster. This skill takes an operator from a config file to a verified running deployment.
One binary does two jobs: generate emits manifests locally; the same image runs run in-cluster. This skill takes an operator from a config file to a verified running deployment.
Prereq: a valid config. If they don't have one, use rmq-generate-config first.
Local binary:
rmq-vertical-scaler generate --config my-config.json --output my-scaler.yaml
No local binary — use the image:
docker run --rm -v "$PWD:/work" -w /work \
ferterahadi/rmq-vertical-scaler:2 generate \
--config my-config.json --output my-scaler.yaml
Flags: -c/--config, -n/--namespace, -s/--service-name, -o/--output, --image, --scaler-name. CLI flags override config values.
The scaler reads RabbitMQ management creds from secret <rmqServiceName>-default-user in the target namespace, keys username + password.
kubectl get secret <service>-default-user -n <namespace>
kubectl create secret generic <service>-default-user -n <namespace> \
--from-literal=username='<user>' --from-literal=password='<pass>'
Show the operator what gets created before applying: ServiceAccount, Role (get/patch/update on rabbitmqclusters, get on secrets, get/create/update/patch on configmaps), RoleBinding, state ConfigMap, PodDisruptionBudget, and the Deployment (runs run).
kubectl apply -f my-scaler.yaml
kubectl rollout status deployment/rmq-vertical-scaler -n <namespace>
kubectl logs -f deployment/rmq-vertical-scaler -n <namespace>
Healthy = logs show it connecting to the RMQ management API and reporting the current profile. Default deployment name is rmq-vertical-scaler (or <scaler-name> if you set --scaler-name).
| Resource | Name |
|---|---|
| Deployment / ServiceAccount / Role / Binding / ConfigMap | rmq-vertical-scaler, -sa, -role, -binding, -config |
| PodDisruptionBudget | <service>-pdb |
| Credentials secret (you supply) | <service>-default-user |
| Image | ferterahadi/rmq-vertical-scaler:latest (override with --image; pin to :2) |
<service>-default-user secret exists → CrashLoop. Check the secret first.--image ...:2 and getting :latest → pin the tag in production.rmq-troubleshoot.Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
npx claudepluginhub ferterahadi/rmq-vertical-scaler --plugin rmq-vertical-scaler