Misogynetes v0.2.1

Patch release: enforce mode no longer lets changes slip through during a webhook rollout, and a crash-looping pod counts as one grievance.

Fixes

• Webhook drains on shutdown (#10): after SIGTERM the webhook keeps serving for --drain (default 5s) before shutting down gracefully. Until now, requests the API server still sent to a terminating pod during a rollout were refused and, with failurePolicy: Ignore, passed unchecked, so in enforce mode a change could slip past the refusal on every webhook rollout.
• A crash loop is one grievance (#11): each restart of a crash-looping pod made a heard problem unheard again, so enforce mode kept refusing fixes the person had already listened to. A grievance now starts at the beginning of the loop, and being heard covers the whole loop.
• Clean krew manifest header (#8): the released misogyn.yaml now names its own version and install URL instead of placeholder text and a v0.1.0 link.

Behaviour change

• A heard problem that keeps going is no longer announced again after 15 minutes. It becomes new only after the pod has been healthy for at least 5 minutes. A restart within 5 minutes of the previous one means the pod is still restarting (was 1 minute), in both the webhook and the CLI.

Docs

• The README installs the latest release instead of v0.1.0 (#9) and describes the crash-loop rule.

Install

• krew: kubectl krew install --manifest-url=https://github.com/tym83/misogynetes/releases/download/v0.2.1/misogyn.yaml
• Helm: helm install misogynetes oci://ghcr.io/tym83/charts/misogynetes --version 0.2.1 (image ghcr.io/tym83/misogynetes-webhook:v0.2.1, linux amd64/arm64)

Full Changelog: v0.2.0...v0.2.1

Misogynetes v0.2.0

Misogynetes, a punishment for misogynists, now works for every client, not only through the kubectl misogyn wrapper.

Highlights

• Server mode as an admission webhook (#6): she shares her grievances (pods in trouble in the namespace) as admission warnings in namespaces labelled misogynetes.dev/mode=warn, and refuses changes while there are fresh grievances only in namespaces labelled misogynetes.dev/mode=enforce (misogynetes.dev/break-glass=<reason> lets a change through). system: identities, kube-system, other service accounts unless opted in, leases, events and Secrets are never touched; failurePolicy: Ignore.
• Helm chart oci://ghcr.io/tym83/charts/misogynetes and image ghcr.io/tym83/misogynetes-webhook:v0.2.0 (linux amd64/arm64), TLS via cert-manager or generated once.
• krew plugin: kubectl krew install --manifest-url=https://github.com/tym83/misogynetes/releases/download/v0.2.0/misogyn.yaml

Fixes

• delete parsing: grievances drop for whatever kubectl says it deleted (selectors, files, -o name), including ReplicaSets, Jobs and pods owned by a deleted workload; --cascade=orphan keeps them (#5).
• Deleted objects are no longer brought up; recovery counts a pod as sorted out one minute after its last restart (was ten); one "we need to talk" line per talk; only a real terminal counts as a terminal, so 2>/dev/null gets plain kubectl (#4).
• e2e on kind for the chart (generated TLS and cert-manager) and a release dry run in CI (#7).

Known issues

• The comment at the top of the released misogyn.yaml still calls its checksums placeholders and shows a v0.1.0 install URL; the checksums themselves are filled in and correct.

Full Changelog: v0.1.0...v0.2.0

Misogynetes v0.1.0

What's Changed

• fix: address review findings on safety invariants, state and framing by @tym83 in #1
• feat: install misogyn as a kubectl krew plugin by @tym83 in #2
• feat: It's Not About the Nail mode — she watches, shares, nags and flirts by @tym83 in #3

New Contributors

• @tym83 made their first contribution in #1

Full Changelog: https://github.com/tym83/misogynetes/commits/v0.1.0