Add nx-cache-proxy image build for fleetshift-poc

[Hyperkid123]

Summary

• Add CI config variant (nx-cache-proxy) to build and mirror the nx-cache-proxy container image from Dockerfile.nx-cache
• Image mirrors to quay.io/stolostron/nx-cache-proxy
• Triggers only on changes to sdk/nx-cache-proxy/ or Dockerfile.nx-cache
• Includes presubmit (PR image mirror), postsubmit (merge + latest tag), and periodic (republish latest every 6h)

Test plan

• make update passes locally
• Prow rehearsal jobs pass on this PR
• After merge, verify image appears at quay.io/stolostron/nx-cache-proxy on next fleetshift-poc change

🤖 Generated with Claude Code

Summary by CodeRabbit

Adds a Fleetshift POC CI configuration for nx-cache-proxy.

• Builds the image with the Go 1.25 Linux builder and arm64 support.
• Mirrors pull request images to quay.io/stolostron/nx-cache-proxy.
• Publishes latest and merge tags after postsubmit jobs.
• Republishes the latest image every six hours with retry support.
• Runs when sdk/nx-cache-proxy/ or Dockerfile.nx-cache changes.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Pro Plus

Run ID: c1f51682-fa44-4a57-99c2-0112d1f96070

📥 Commits

Reviewing files that changed from the base of the PR and between c91a2bb and d2ef614.

⛔ Files ignored due to path filters (3)

• ci-operator/jobs/fleetshift/fleetshift-poc/fleetshift-fleetshift-poc-main-periodics.yaml is excluded by !ci-operator/jobs/**
• ci-operator/jobs/fleetshift/fleetshift-poc/fleetshift-fleetshift-poc-main-postsubmits.yaml is excluded by !ci-operator/jobs/**
• ci-operator/jobs/fleetshift/fleetshift-poc/fleetshift-fleetshift-poc-main-presubmits.yaml is excluded by !ci-operator/jobs/**

📒 Files selected for processing (1)

• ci-operator/config/fleetshift/fleetshift-poc/fleetshift-fleetshift-poc-main__nx-cache-proxy.yaml

---

Walkthrough

Adds a Fleetshift POC CI configuration for building, mirroring, and republishing the nx-cache-proxy arm64 image. The configuration includes resource requests, retry settings, scheduled latest image publishing, and generated repository metadata.

Changes

Fleetshift nx-cache-proxy image pipeline

Layer / File(s)	Summary
Image pipeline configuration ci-operator/config/fleetshift/fleetshift-poc/fleetshift-fleetshift-poc-main__nx-cache-proxy.yaml	Adds Go 1.25 Linux builds, Dockerfile-triggered arm64 image builds, resource requests, PR and postsubmit image mirroring, scheduled latest image republishing with retries, and generated branch, repository, and variant metadata.

Estimated code review effort: 2 (Simple) | ~10 minutes

🚥 Pre-merge checks | ✅ 15

✅ Passed checks (15 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the added nx-cache-proxy image build configuration for fleetshift-poc.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
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.
Stable And Deterministic Test Names	✅ Passed	The PR changes only CI YAML and generated Prow jobs; searches found no Ginkgo It, Describe, Context, or When test titles, dynamic or otherwise.
Test Structure And Quality	✅ Passed	The PR changes only YAML CI configuration and generated Prow job files; it adds no Ginkgo test code or It blocks, so this check is not applicable.
Microshift Test Compatibility	✅ Passed	The pull request changes only four YAML CI configuration files; no new Ginkgo e2e tests or test references to MicroShift-unsupported APIs are present.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	The pull request changes only CI YAML configuration and generated Prow jobs; it adds no Ginkgo e2e tests requiring SNO compatibility review.
Topology-Aware Scheduling Compatibility	✅ Passed	The PR changes only ci-operator configuration and generated Prow jobs; it adds no deployment, operator, controller, or topology-sensitive scheduling constraints.
Ote Binary Stdout Contract	✅ Passed	The PR changes only four YAML CI configuration/generated job files; it adds no OTE binary or process-level Go test setup that can write to stdout.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	The PR changes only YAML CI configuration and generated Prow job files; it adds no Ginkgo e2e tests or test-side IPv4 or external-connectivity assumptions.
No-Weak-Crypto	✅ Passed	The PR adds only YAML CI configuration and generated jobs; added-line scans found no MD5, SHA1, DES, RC4, 3DES, Blowfish, ECB, crypto implementation, or secret comparison.
Container-Privileges	✅ Passed	The new CI YAML and referenced image-mirror workflow contain no privileged, hostPID, hostNetwork, hostIPC, SYS_ADMIN, allowPrivilegeEscalation, or root-user settings.
No-Sensitive-Data-In-Logs	✅ Passed	The added configuration contains only image names, paths, scheduling, resources, and non-secret registry metadata; it adds no logging or sensitive values.

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

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Hyperkid123

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• ci-operator/config/fleetshift/fleetshift-poc/OWNERS [Hyperkid123]
• ci-operator/jobs/fleetshift/fleetshift-poc/OWNERS [Hyperkid123]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-merge-bot]

[REHEARSALNOTIFIER]
@Hyperkid123: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name	Repo	Type	Reason
pull-ci-fleetshift-fleetshift-poc-main-nx-cache-proxy-images	fleetshift/fleetshift-poc	presubmit	Presubmit changed
pull-ci-fleetshift-fleetshift-poc-main-nx-cache-proxy-pr-image-mirror	fleetshift/fleetshift-poc	presubmit	Presubmit changed
periodic-ci-fleetshift-fleetshift-poc-main-nx-cache-proxy-republish-latest	N/A	periodic	Periodic changed

Prior to this PR being merged, you will need to either run and acknowledge or opt to skip these rehearsals.

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

[openshift-ci]

@Hyperkid123: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.