abahmed/kwatch v1.0.0-rc.22 on GitHub

v1.0.0-rc.22

Upgrading from 0.10.x

Installer (recommended): run
/bin/bash -c "$(curl -fsSL https://kwatch.dev/kwatch.sh)". It
finds a 0.10.x install and offers to recreate the Deployment; your
configuration and Secrets are kept.
Helm: helm upgrade works with your 0.10.x values file. The old
service block is accepted and ignored. If you installed 0.10.x with Helm 4
(server-side apply), add --server-side=false to the upgrade, or
Kubernetes rejects the old RollingUpdate settings.
kubectl apply -f deploy/deploy.yaml: the Deployment selector
changed (it now also matches app.kubernetes.io/instance: kwatch),
and Kubernetes does not allow a selector to change. The configuration
also moved from the ConfigMap kwatch to the Secret kwatch. Create
the Secret from your config.yaml (credentials as described in the
upgrade guide), delete the old Deployment, then apply:
```
kubectl -n kwatch create secret generic kwatch \
  --from-file=config.yaml=config.yaml
kubectl delete deployment kwatch -n kwatch
kubectl apply -f deploy/deploy.yaml
```

See Upgrading to 1.0 for every configuration change.

Jitter cluster check-ins to spread load on the Worker (#563) (79a72b2)
Say check-ins run every 30 minutes in the config catalog (#562) (9b0978e)

See the full diff since v1.0.0-rc.21.

Release integrity

Source tag: v1.0.0-rc.22
Source commit: 470c3424923e257f1bc2d28a5f4cec48287ecbfc
Image: ghcr.io/abahmed/kwatch@sha256:6c1c16d98c471809b43e23e99cf98478ac34aa1dce452e3a79c400a90a8fac11
Verification files: checksums, signed checksums, manifest, installer checksums (signed)
SBOMs: kwatch-v1.0.0-rc.22-source-sbom.cdx.json and kwatch-v1.0.0-rc.22-image-sbom.cdx.json

Verify the image with:

cosign verify \
  --certificate-oidc-issuer=https://token.actions.githubusercontent.com \
  --certificate-identity-regexp='^https://github.com/abahmed/kwatch/.github/workflows/publish.yml@' \
  ghcr.io/abahmed/kwatch@sha256:6c1c16d98c471809b43e23e99cf98478ac34aa1dce452e3a79c400a90a8fac11