Added a job for ibm-powervs-block-csi-driver image build and push to GCR

[Madhan-SWE]

Added a job for building ibm-powervs-block-csi-driver image and pushing to Google Container Registry.

[k8s-ci-robot]

Hi @Madhan-SWE. Thanks for your PR.

I'm waiting for a kubernetes 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. Regular contributors should join the org to skip this step.

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.

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/test-infra repository.

[BenTheElder]

/ok-to-test

[mkumatag]

/hold till we get cloudbuild file created and makefile enhanced to handle multi-arch image build

[mkumatag]

Now we have the required files via kubernetes-sigs/ibm-powervs-block-csi-driver#124,

/unhold
/lgtm

[mkumatag]

@Madhan-SWE can you squash the changes?

[mkumatag]

/lgtm
/approve

[mkumatag]

/assign @mpherman2 @BenTheElder

[mkumatag]

/retest

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Madhan-SWE, mkumatag, mpherman2

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:

• config/jobs/image-pushing/OWNERS [mpherman2]

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

[k8s-triage-robot]

The Kubernetes project has merge-blocking tests that are currently too flaky to consistently pass.

This bot retests PRs for certain kubernetes repos according to the following rules:

• The PR does have any do-not-merge/* labels
• The PR does not have the needs-ok-to-test label
• The PR is mergeable (does not have a needs-rebase label)
• The PR is approved (has cncf-cla: yes, lgtm, approved labels)
• The PR is failing tests required for merge

You can:

• Review the full test history for this PR
• Prevent this bot from retesting with /lgtm cancel or /hold
• Help make our tests less flaky by following our Flaky Tests Guide

/retest

[k8s-triage-robot]

The Kubernetes project has merge-blocking tests that are currently too flaky to consistently pass.

This bot retests PRs for certain kubernetes repos according to the following rules:

• The PR does have any do-not-merge/* labels
• The PR does not have the needs-ok-to-test label
• The PR is mergeable (does not have a needs-rebase label)
• The PR is approved (has cncf-cla: yes, lgtm, approved labels)
• The PR is failing tests required for merge

You can:

• Review the full test history for this PR
• Prevent this bot from retesting with /lgtm cancel or /hold
• Help make our tests less flaky by following our Flaky Tests Guide

/retest

[k8s-ci-robot]

@Madhan-SWE: Updated the job-config configmap in namespace default at cluster test-infra-trusted using the following files:

• key k8s-staging-cloud-provider-ibm.yaml using file config/jobs/image-pushing/k8s-staging-cloud-provider-ibm.yaml

In response to this:

Added a job for building ibm-powervs-block-csi-driver image and pushing to Google Container Registry.

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/test-infra repository.