ROB-997 Upgrade kubewatch image to v2.16.0

[naomi-robusta]

Summary

Updates the kubewatch forwarder deployment image version from v2.14.0 to v2.16.0.

Changes

• Bumped kubewatch image version from v2.14.0 to v2.16.0 in the Helm values configuration

Details

This upgrade brings the latest kubewatch version to the robusta forwarder deployment, which may include bug fixes, performance improvements, and new features from the kubewatch project.

https://claude.ai/code/session_01GzZp8kPXKYjXuxY1oN1aU8

[github-actions]

✅ Docker image ready for f800cfc (built in 41s)

• us-central1-docker.pkg.dev/robusta-development/temporary-builds/robusta-runner:f800cfc

⚠️ Warning: does not support ARM (ARM images are built on release only - not on every PR)

Use this tag to pull the image for testing.

📋 Copy commands

⚠️ Temporary images are deleted after 30 days. Copy to a permanent registry before using them:

gcloud auth configure-docker us-central1-docker.pkg.dev
docker pull us-central1-docker.pkg.dev/robusta-development/temporary-builds/robusta-runner:f800cfc
docker tag us-central1-docker.pkg.dev/robusta-development/temporary-builds/robusta-runner:f800cfc me-west1-docker.pkg.dev/robusta-development/development/robusta-runner-dev:f800cfc
docker push me-west1-docker.pkg.dev/robusta-development/development/robusta-runner-dev:f800cfc

Patch Helm values in one line:

helm upgrade --install robusta robusta/robusta \
  --reuse-values \
  --set runner.image=me-west1-docker.pkg.dev/robusta-development/development/robusta-runner-dev:f800cfc

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 86542863-1c4c-452b-8b27-702b82085fd9

📥 Commits

Reviewing files that changed from the base of the PR and between 314f520 and a8ef37a.

📒 Files selected for processing (1)

• helm/robusta/values.yaml

Included review availability: Your plan provides up to 8 included reviews per hour; 7 remain after this review.

---

Walkthrough

The Helm chart default kubewatch image tag changes from v2.14.0 to v2.16.0.

Changes

Kubewatch image update

Layer / File(s)	Summary
Update default kubewatch image helm/robusta/values.yaml	The default kubewatch image changes from kubewatch:v2.14.0 to kubewatch:v2.16.0.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to a8ef3

This is a localized kubewatch image-version update with no actionable merge-blocking risk remaining beyond normal checks and review.

Suggested reviewers: avi-robusta, moshemorad

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Title check	✅ Passed	The title clearly identifies the kubewatch image upgrade from the changeset.
Description check	✅ Passed	The description accurately explains the kubewatch image version update in the Helm configuration.

✨ Finishing Touches 💡 1

🛠️ Fix failing CI checks 💡

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch claude/kubewatch-codex-h12-cloudevent-m414u3

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[naomi-robusta]

Pre-commit checks is red here, but not because of this diff — it fails on master too, and this PR is a one-line image-tag change.

The poetry-lock hook rewrites poetry.lock, so the hook reports a modified file and exits 1:

-lock-version = "2.1"
+lock-version = "2.0"
-groups = ["main"]        (stripped from every package entry)

.pre-commit-config.yaml pins python-poetry/poetry at 1.8.5, which writes lock-version = "2.0". The lockfile on master is at lock-version = "2.1", which only Poetry 2.x produces — so the hook rewrites it on every run and can never pass.

Where it came from:

master commit	test_robusta.yaml
314f520b — ROB-1207 bump cryptography to ^50.0.0 (#2155)	❌ failure (Pre-commit checks, sole failing job)
acf0db9a — parent, and this branch's base	✅ success

#2155 regenerated the lockfile under Poetry 2.x. PR checks build the merge with master, so that lockfile is in this PR's checkout and the failure follows it here.

Not fixing it in this PR — regenerating a lockfile has nothing to do with a kubewatch image bump, and folding it in would hide a dependency change inside a security bump. The fix belongs on master: re-run poetry lock --no-update under Poetry 1.8.5 to bring the file back to lock-version = "2.0" (or, if the intent is to move to Poetry 2.x, raise the rev: in .pre-commit-config.yaml to match — but that is a repo-wide decision, not a side effect of a CVE bump).

Check Secrets passed; run_tests was skipped.

---

Generated by Claude Code