Update bundle to match latest snapshot for 0.22.1

[dfarrell07]

Bundle had mixed SHAs from different snapshots, blocking stage release:

• Operator: sha256:64f4f313... from snapshot submariner-0-22-20260214-082638-000 (bot PR Update submariner-operator-0-22 to 64f4f31 #3891)
• Other 6 components: stale SHAs from snapshot submariner-0-22-20260212-181224-000 (PR Update bundle to 0.22.1 #3873)

Bot PR #3891 only updated operator component, leaving others at old SHAs
from PR #3873. This mixed state doesn't match any complete Konflux
snapshot.

Updates 6 components (gateway, route-agent, globalnet, lighthouse-agent,
lighthouse-coredns, nettest) to match snapshot
submariner-0-22-20260216-213302-000-va. Operator SHA unchanged (already
matches valid snapshot submariner-0-22-20260214-082638-000).

Summary by CodeRabbit

• Chores
  • Updated container image references for Submariner and Lighthouse components (gateway, route agent, globalnet, Lighthouse agents, CoreDNS, nettest and metrics proxy) to newer digests to ensure up-to-date runtime images.
  • Updated build/timestamp metadata in manifests to reflect the latest build.

[submariner-bot]

🤖 Created branch: z_pr3900/dfarrell07/bundle-sha-update-0.22.1
🚀 Full E2E won't run until the "ready-to-test" label is applied. I will add it automatically once the PR has 2 approvals, or you can add it manually.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

---

Walkthrough

Updated image digests and the createdAt timestamp in the Submariner bundle and kustomize patches; no functional or control-flow changes.

Changes

Cohort / File(s)	Summary
Bundle CSV bundle/manifests/submariner.clusterserviceversion.yaml	Bumped createdAt and updated multiple RELATED_IMAGE and relatedImages entries to new sha256 image digests (gateway, route-agent, globalnet, lighthouse-agent, lighthouse-coredns, nettest, metrics-proxy).
Kustomization config/bundle/kustomization.yaml	Updated commonAnnotations.createdAt timestamp only.
Related-images patch config/manager/patches/related-images.deployment.config.yaml	Replaced several RELATED_IMAGE_* env values with new sha256 digests (gateway, route-agent, globalnet, lighthouse-agent, lighthouse-coredns, nettest, metrics-proxy); patch structure unchanged.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• Update Submariner dependencies to v0.23.0-rc0 #3854: Modifies bundle CSV RELATED_IMAGE entries and image references.
• Update bundle to 0.22.1 #3873: Updates CSV, kustomization, and related-images patch with new image digests and timestamps.
• Substitute containerImage annotation in bundle #3841: Changes image references in the CSV and related-images config.

Suggested labels

ready-to-test

Suggested reviewers

• Oats87
• skitt
• sridhargaddam
• vthapar
• tpantelis

🚥 Pre-merge checks | ✅ 4

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and specifically summarizes the main change: updating container image digests in the bundle to match a newer Konflux snapshot for version 0.22.1, which is the primary purpose of this PR.
Merge Conflict Detection	✅ Passed	✅ No merge conflicts detected when merging into release-0.22
Actionable Comments Resolved	✅ Passed	No unresolved actionable comments found in code changes; only standard automation requirement for E2E test triggering.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

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 and usage tips.}

[submariner-bot]

🤖 Closed branches: [z_pr3900/dfarrell07/bundle-sha-update-0.22.1]

[dfarrell07]

@tpantelis @skitt Seems like a bug in the setup? Merged with no non-author human vote.

[skitt]

@tpantelis @skitt Seems like a bug in the setup? Merged with no non-author human vote.

Yup, that shouldn’t happen…

[tpantelis]

@tpantelis @skitt Seems like a bug in the setup? Merged with no non-author human vote.

Yup, that shouldn’t happen…

You must have had auto-merge enabled. Now that we'v e scaled back the criteria for release branches to one non-code owner review, a CodeRabbit approval will auto-merge it so we probably want to avoid enabling that for human-created PRs.

[dfarrell07]

a CodeRabbit approval will auto-merge

That seems like a security issue, right? Any human could merge into release branches if CI and Coderabbit approve (and I think you can just command Coderabbit to approve).

[skitt]

a CodeRabbit approval will auto-merge

That seems like a security issue, right? Any human could merge into release branches if CI and Coderabbit approve (and I think you can just command Coderabbit to approve).

I thought the idea was to disable Coderabbit reviews on release branches, did I get that wrong?