kubernetes-operator — Claude Code plugin: CRDs, reconcile, audit
Operator-pattern discipline for Kubernetes: a CRD validator, a reconcile-loop linter and a Capability Level auditor. Useful once you are writing the controller, not still picking a framework.
/plugin marketplace add alirezarezvani/claude-skills
/plugin install kubernetes-operator@claude-code-skillsWhat kubernetes-operator does
The plugin covers one slice of Kubernetes work — the Operator pattern. Three stdlib Python tools ship with it: crd_validator.py checks a CRD, reconcile_lint.py scans a controller for the usual reconcile bugs, operator_capability_audit.py scores an operator against OperatorHub levels. Four references back them up: the operator pattern itself, CRD design, reconcile patterns, and a framework comparison covering controller-runtime, kubebuilder, operator-sdk, metacontroller and KOPF.
Templates are included too — a production CRD in YAML and a Go controller skeleton, both passing the linters. The /operator-audit slash command runs all three scripts and writes a report. Run it before the first push to a cluster: the linter catches missing finalizers, blocking calls, status drift, RBAC over-grants and a dropped requeue, which are painful to trace from logs later.
This is not a general Kubernetes kit. For Helm charts, kubectl work, cluster security or cloud architecture the author points at other skills, so pulling it in for everything is a waste. The tools run by hand from the skill directory and need no API keys or external services.
What it helps with
- validate a CRD before merge instead of after it breaks in a cluster
- spot blocking calls and a missing requeue in a reconcile function
- score an operator against OperatorHub levels before a public release
- compare controller frameworks before committing to one
- start from a working CRD and Go controller skeleton
Example prompts for the agent
- run
/operator-auditon this operator and show me the report - validate
config/crd/myapp.yamland explain what the CRD validator flags - lint
controllers/myapp_controller.goin strict mode
How to install kubernetes-operator
Plugin marketplace
/plugin marketplace add alirezarezvani/claude-skills/plugin install kubernetes-operator@claude-code-skillsStep by step, with commands for each platform: Claude Code plugins: marketplaces, installing, and building your own
From the same set394
The whole set →Similar
Nearby in DevOps and infrastructure
All plugins for DevOps and infrastructure →Questions about kubernetes-operator
How do I install kubernetes-operator in Claude?
From the marketplace: run /plugin marketplace add alirezarezvani/claude-skills, then /plugin install kubernetes-operator@claude-code-skills.
What does kubernetes-operator do?
It supports Kubernetes Operator work: validating CRDs, linting reconcile loops, auditing OperatorHub capability levels, plus references and skeletons.
How is it different from general Kubernetes skills?
It targets the Operator pattern only. Helm chart authoring, kubectl operations, cluster security and cloud architecture live in separate skills in the same repo.
Source text
kubernetes-operator · MIT
# Kubernetes Operator
End-to-end discipline for building Kubernetes Operators correctly. Catches the recurring reconcile-loop bugs (missing finalizers, blocking calls, status drift, RBAC over-grants, no requeue) before they reach a cluster.
## What's inside
- **3 stdlib Python tools** — CRD validator, reconcile-loop linter, OperatorHub capability auditor
- **4 reference docs** — operator pattern, CRD design, reconcile patterns, framework comparison
- **Asset templates** — production CRD YAML + Go controller skeleton (both pass the linters)
- **`/operator-audit` slash command** — runs all 3 tools and produces a report
## Install
```bash
# Via Claude Code marketplace
/plugin install kubernetes-operator
# Or clone the repo
git clone https://github.com/alirezarezvani/claude-skills.git
cd claude-skills/engineering/kubernetes-operator
```
## Quick start
```bash
SKILL=engineering/kubernetes-operator/skills/kubernetes-operator
python "$SKILL/scripts/crd_validator.py" --crd config/crd/myapp.yaml
python "$SKILL/scripts/reconcile_lint.py" --controller controllers/myapp_controller.go
python "$SKILL/scripts/operator_capability_audit.py" --operator-dir .
```
## Scope
This is the **Operator pattern** specifically. For other Kubernetes work:
- Helm chart authoring → `helm-chart-builder`
- Kubectl operations / blue-green deploys → `senior-devops`
- General k8s security → `cloud-security`
- Cloud architecture → `aws-solution-architect`, `azure-cloud-architect`, `gcp-cloud-architect`
## Key principles
1. **Reconcile is idempotent**, declarative, and bounded in time
2. **Status subresource is non-negotiable** — without it, status updates loop spec reconciles
3. **Finalizers protect external resources** — cascade deletion is the operator pattern's free gift, but only for owned k8s resources
4. **RBAC is least-privilege** — controllers shouldn't read secrets they don't need
5. **Capability levels are an SLA**, not a label — aim for L3 (Full Lifecycle) before public release
## Skill structure
```
kubernetes-operator/
├── README.md
├── .claude-plugin/plugin.json
└── skills/kubernetes-operator/
├── SKILL.md
├── scripts/
│ ├── crd_validator.py
│ ├── reconcile_lint.py
│ └── operator_capability_audit.py
├── references/
│ ├── operator_pattern.md
│ ├── crd_design.md
│ ├── reconcile_loop.md
│ └── tooling_landscape.md
└── assets/
├── crd_template.yaml
└── reconcile_skeleton.go
```
## Verifiable success
A team using this skill should achieve:
- 100% of new CRDs pass `crd_validator.py` before merge
- All reconcile functions pass `reconcile_lint.py` strict mode
- Operators reach OperatorHub Capability Level 3 before public release
- Mean time to fix a reconcile bug: <1 day (no infinite loops in production)
## License
MIT — see repo root LICENSE.
© Alireza Rezvani · MIT · alirezarezvani/claude-skills
