fix(docker): update base images to resolve ACS CVE alert

[platex-rehor-bot]

Description

Update container base images to resolve ACS_CVSS_CRITICAL vulnerability alert for quickstarts on cluster hccp01ue1.

RHCLOUD-48004

Changes:

• Builder image: ubi9/go-toolset:1.25.8-1776370298 → 1.26.2-1779886993
• GOTOOLCHAIN: go1.25.9 → go1.26.2 (aligned with builder image)
• Tekton pipeline: updated go-toolset image reference to match

The runtime stage (ubi9-minimal:latest) will pull fresh security patches on rebuild, resolving the critical CVEs flagged by ACS.

Grype scan results: Both new base images scanned clean — zero fixable CVEs.

Note: Mintmaker PRs #453 and #455 propose similar base image updates. This PR is focused specifically on resolving the ACS CVE alert.

---

How to test locally

No functional changes — only base image updates. Verify:

1. make generate && make test — all tests pass
2. Container builds successfully with updated images
3. Konflux CI passes

---

Anything reviewers should know?

• Go version bump from 1.25.8 to 1.26.2 in builder image. GOTOOLCHAIN=go1.26.2 ensures the image's Go is used directly.
• go.mod still specifies go 1.25.9 — Go 1.26 is fully backward compatible with 1.25 modules.
• The pre-existing covdata tool error in make test is unrelated to this change.

---

Checklist

• Tests: new/updated tests cover the change
• API: spec updated if endpoints changed (or N/A)
• Migrations: backwards compatible if schema changed (or N/A)
• Dependencies: no known impact to dependent services
• Security: reviewed against secure coding checklist (or N/A)

AI disclosure

Assisted by: Claude Code

[coderabbitai]

Warning

Review limit reached

@platex-rehor-bot, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 21 minutes and 14 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

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.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Enterprise

Run ID: 754a01a6-5fd7-4560-ac19-fa8c54b39894

📥 Commits

Reviewing files that changed from the base of the PR and between 8585343 and 57e80ae.

⛔ Files ignored due to path filters (1)

• go.sum is excluded by !**/*.sum

📒 Files selected for processing (3)

• .tekton/quickstarts-pull-request.yaml
• Dockerfile
• go.mod

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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