Added optional presubmit check-provision-k8s-1.30-s390x

[chandramerla]

What this PR does / why we need it:
This PR adds optional presubmit prow job named check-provision-k8s-1.30-s390x, which is used for checking the provisioning of k8s 1.30 provider on s390x arch. As we've a PR #1252 enabling k8s 1.30 provider on s390x, this prow job once merged can be used in that job as presubmit check.

Special notes for your reviewer:
Created the PR as discussed here

Checklist

This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.

• Design: A design document was considered and is present (link) or not required
• PR: The PR description is expressive enough and will help future contributors
• Code: Write code that humans can understand and Keep it simple
• Refactor: You have left the code cleaner than you found it (Boy Scout Rule)
• Upgrade: Impact of this change on upgrade flows was considered and addressed if required
• Testing: New code requires new unit tests. New features and bug fixes require at least on e2e test
• Documentation: A user-guide update was considered and is present (link) or not required. You want a user-guide update if it's a user facing feature / API change.
• Community: Announcement to kubevirt-dev was considered

Release note:

NONE

[kubevirt-bot]

Hi @chandramerla. Thanks for your PR.

PRs from untrusted users cannot be marked as trusted with /ok-to-test in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all.

I understand the commands that are listed here.

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.

[chandramerla]

/cc @brianmcarey
/sig ci

[brianmcarey]

/test all

[brianmcarey]

/approve

[kubevirt-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: brianmcarey

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

The pull request process is described here

Needs approval from an approver in each of these files:

• github/ci/prow-deploy/files/jobs/kubevirt/kubevirtci/OWNERS [brianmcarey]

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

[kubevirt-bot]

@chandramerla: Updated the job-config configmap in namespace kubevirt-prow at cluster default using the following files:

• key kubevirtci-presubmits.yaml using file github/ci/prow-deploy/files/jobs/kubevirt/kubevirtci/kubevirtci-presubmits.yaml

In response to this:

What this PR does / why we need it:
This PR adds optional presubmit prow job named check-provision-k8s-1.30-s390x, which is used for checking the provisioning of k8s 1.30 provider on s390x arch. As we've a PR #1252 enabling k8s 1.30 provider on s390x, this prow job once merged can be used in that job as presubmit check.

Special notes for your reviewer:
Created the PR as discussed here

Checklist

This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.

• Design: A design document was considered and is present (link) or not required
• PR: The PR description is expressive enough and will help future contributors
• Code: Write code that humans can understand and Keep it simple
• Refactor: You have left the code cleaner than you found it (Boy Scout Rule)
• Upgrade: Impact of this change on upgrade flows was considered and addressed if required
• Testing: New code requires new unit tests. New features and bug fixes require at least on e2e test
• Documentation: A user-guide update was considered and is present (link) or not required. You want a user-guide update if it's a user facing feature / API change.
• Community: Announcement to kubevirt-dev was considered

Release note:

NONE

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.

[brianmcarey]

Sorry - I missed this in the initial review - the s390x cluster doesn't have the image proxy so this preset will cause the job to fail to schedule.

Can you remove this preset in a follow up?

[chandramerla]

@brianmcarey

I've created this PR #3684

Do we've to remove this label also for publish provider jobs for s390x at #3566 ?

[chandramerla]

@brianmcarey Any doc which I can read to know more about docker mirror proxy use-case we use it for?

[brianmcarey]

This doc gives an overview of the services we use on the main clusters - https://github.com/kubevirt/project-infra/blob/main/docs/infrastructure-components.md