Migrate cluster-api-provider-cloudstack jobs to eks-prow-build-cluster

[chrisdoherty4]

See #29722

This PR does not migrate the smoke test job as it creates clusters using an external CloudStack instance. The job is a trigger for an external system so its possible it'll work but we can deal with it separately.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: chrisdoherty4

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/kubernetes-sigs/cluster-api-provider-cloudstack/OWNERS [chrisdoherty4]

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

[chrisdoherty4]

/assign @rohityadavcloud @g-gaston @weizhouapache

[rjsadow]

Hi @chrisdoherty4, the PR title says these are moving to eks-prow-build-cluster but it looks like k8s-infra-prow-build is defined as the clusters. Did you mean to make those eks?

[weizhouapache]

@chrisdoherty4
code looks good to me.
do we need to mgirate capi-provider-cloudstack-presubmit-e2e-smoke-test as well ?

[chrisdoherty4]

Hi @chrisdoherty4, the PR title says these are moving to eks-prow-build-cluster but it looks like k8s-infra-prow-build is defined as the clusters. Did you mean to make those eks?

@rjsadow Thank you, it should've been eks-prow-build-cluster. Updated.

@chrisdoherty4 code looks good to me. do we need to mgirate capi-provider-cloudstack-presubmit-e2e-smoke-test as well ?

@weizhouapache As noted in the OP, I refrained from touching that job as it integrates with an external system and the general advice is to avoid migrating those right now.

[weizhouapache]

@weizhouapache As noted in the OP, I refrained from touching that job as it integrates with an external system and the general advice is to avoid migrating those right now.

@chrisdoherty4
the PR kubernetes-sigs/cluster-api-provider-cloudstack#259 describes what smoke test does, which may not require extra configurations or external systems. It can be migrated in another PR.

[weizhouapache]

/lgtm

[k8s-ci-robot]

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

• key capi-provider-cloudstack-presumbit.yaml using file config/jobs/kubernetes-sigs/cluster-api-provider-cloudstack/capi-provider-cloudstack-presumbit.yaml

In response to this:

See #29722

This PR does not migrate the smoke test job as it creates clusters using an external CloudStack instance. The job is a trigger for an external system so its possible it'll work but we can deal with it separately.

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.

[chrisdoherty4]

@weizhouapache As noted in the OP, I refrained from touching that job as it integrates with an external system and the general advice is to avoid migrating those right now.

@chrisdoherty4 the PR kubernetes-sigs/cluster-api-provider-cloudstack#259 describes what smoke test does, which may not require extra configurations or external systems. It can be migrated in another PR.

Thanks @weizhouapache, I'll raise another PR shortly.