docs: trigger image-builder presubmit validation

[Srishti-j18]

What type of PR is this?

/kind test

What this PR does / why we need it:
This PR makes a small documentation-only change under test-infra/image-builder/ to verify that the new pull-kubespray-kubevirt-image-builder-validate presubmit appears and runs on Kubespray PRs.

Which issue(s) this PR fixes:

NA

Special notes for your reviewer:

This is to validate the newly merged Prow presubmit job from:

• Kubespray image-builder presubmit canary build validation kubernetes/test-infra#36692

Does this PR introduce a user-facing change?:

NONE

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: Srishti-j18
Once this PR has been reviewed and has the lgtm label, please assign ant31 for approval. For more information see the Code Review Process.

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

Details

Needs approval from an approver in each of these files:

• test-infra/image-builder/OWNERS

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

[k8s-ci-robot]

Hi @Srishti-j18. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Tip

We noticed you've done this a few times! Consider joining the org to skip this step and gain /lgtm and other bot rights. We recommend asking approvers on your previous PRs to sponsor you.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[Copilot]

Pull request overview

Documentation-only change to clarify that the test-infra/image-builder validation make targets correspond to what’s exercised by the Kubespray image-builder presubmit validation.

Changes:

• Add a note in the CI Validation section indicating the validate targets are used by the Kubespray image-builder presubmit job.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Srishti-j18]

need /ok-to-test

[Srishti-j18]

/cc @tico88612 @VannTen @yankay

[tico88612]

/ok-to-test

[Srishti-j18]

/retest-failed

[Srishti-j18]

/retest

[k8s-ci-robot]

@Srishti-j18: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-kubespray-kubevirt-image-builder-validate	b1fadf9	link	true	/test pull-kubespray-kubevirt-image-builder-validate

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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.

[Srishti-j18]

The new presubmit is now triggering correctly on a Kubespray PR, but it fails when running make validate-single image_name=ubuntu-2404 because the job cannot reach the configured builder host from hosts.ini (image-builder-1 shows as unreachable). So the current blocker is builder-host access from the Prow environment, not the presubmit wiring itself.

[VannTen]

Could we use a build tool which does not require docker daemon access or other privileges ?
For example in .gitlab-ci/build.yml we're using moby/buildkit:rootless which works well, and doesn't require any access to another builder.

[Srishti-j18]

That sounds like a better direction.

The current blocker is that the presubmit depends on SSH access to the remote builder host from hosts.ini, which Prow does not have. Running the validation locally inside CI would avoid that dependency and fit Prow much better.

The current validation flow does more than just the container build, though. It also:

• downloads the cloud image
• converts/resizes it with qemu-img
• then builds the container image

So I’ll look into whether we can adapt the validation flow to run locally in CI, including theqemu-imgpart, or whether that flow should be split. I’ll take that up as the next follow-up.