deploy(prod): promote backend-prod pin → KSV hardening

[F-U-R-Y]

Carries the backend securityContext hardening (gitops #20) verified in
test: pod nonroot 65532 + RuntimeDefault seccomp, container no-priv-esc +
drop-ALL + read-only rootfs; same image tag. frontend-prod and
platform-observability pins unmoved (the frontend required-tag guard
renders identical output).

What this deploys: compare view — for charts/backend, the #20 securityContext hardening; the image tag is unchanged, so this is a pod restart under the new context, not a version change.

Verified in test (2026-07-13): pod Running clean under the hardened context, live spec matches, /healthz 200 through the Ingress, auth path exercised, zero unexpected log errors. Uptime probes stayed green.

After merge: I kubectl apply the manifest, you manual-Sync backend-prod — the api.collectiongeek.app probe (watched from both clusters) covers the rollover.

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

@F-U-R-Y, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 37 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: a42771bf-1e18-4ca4-98fa-348ddf645ff7

📥 Commits

Reviewing files that changed from the base of the PR and between d6b1ad5 and 5fb2aa8.

📒 Files selected for processing (1)

• argocd/backend-prod.yaml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch promote/backend-prod-hardening

---

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.}