Added the updown-ibmcloud.sh script path to the IBM Cloud presubmit jobs

[varshadeshmane92]

• Updated the IBM Cloud presubmit job to call the updown-ibmcloud.sh script
  instead of using inline commands.
• This change automates the end-to-end (E2E) testing for IBM Cloud PowerVS
  while making the job definition cleaner and easier to maintain.

[k8s-ci-robot]

Hi @varshadeshmane92. 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.

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.

[Rajalakshmi-Girish]

@varshadeshmane92 recently there were changes to the kubetest2 TF deployer setup commands via kubernetes-sigs/provider-ibmcloud-test-infra#91

With this update, running make install-deployer-tf installs prebuilt binaries from IBM COS. However, the purpose of the pull-provider-ibmcloud-test-infra-kubernetes job is to validate the changes introduced in provider-ibmcloud-test-infra repo.

To ensure this, the job should build the binaries dynamically during execution and then use them for cluster testing.

Could you please update the updown-ibmcloud.sh script accordingly, following the approach in the PR: #36853
Do run a test-pj before requesting review here.

@kishen-v

[varshadeshmane92]

@varshadeshmane92 recently there were changes to the kubetest2 TF deployer setup commands via kubernetes-sigs/provider-ibmcloud-test-infra#91
With this update, running make install-deployer-tf installs prebuilt binaries from IBM COS. However, the purpose of the pull-provider-ibmcloud-test-infra-kubernetes job is to validate the changes introduced in provider-ibmcloud-test-infra repo.
To ensure this, the job should build the binaries dynamically during execution and then use them for cluster testing.
Could you please update the updown-ibmcloud.sh script accordingly, following the approach in the PR: #36853 Do run a test-pj before requesting review here.
@kishen-v

Done.
Resolve this.

[kishen-v]

/lgtm
/hold
/cc @Rajalakshmi-Girish

[varshadeshmane92]

/test pull-test-infra-verify-lint

[k8s-ci-robot]

@varshadeshmane92: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

Details

In response to this:

/test pull-test-infra-verify-lint

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.

[k8s-ci-robot]

New changes are detected. LGTM label has been removed.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: varshadeshmane92
Once this PR has been reviewed and has the lgtm label, please ask for approval from kishen-v. 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:

• config/jobs/kubernetes/cloud-provider-ibmcloud/OWNERS

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

[kishen-v]

/ok-to-test