Investigate usage of VMC for CAPV tests

[ameukam]

CAPV currently run tests inside VMware-owned AWS account using vSphere Cloud on AWS service(VMC). The service can be used on the community infrastructure.

It's still unclear to me how VMC is integrated to VMware Cloud.

Update: projects eligible :

• https://github.com/kubernetes-sigs/cluster-api-provider-vsphere
• https://github.com/kubernetes-sigs/image-builder
• https://github.com/kubernetes/cloud-provider-vsphere

/sig cluster-lifecycle
/area infra/aws
/priority important-longterm
/milestone v1.29

[ameukam]

cc @sbueringer @chrischdi @killianmuldoon @fabriziopandini

[ameukam]

cc @dims

[dims]

supportive for sure. Let's come up with some numbers for how much it costs for helping with the decision making process.

[chrischdi]

*Adding cloud-provider-vsphere to the list, because they use the same environment / capabilities (share the same environment)

[sbueringer]

Also image-builder

[ameukam]

supportive for sure. Let's come up with some numbers for how much it costs for helping with the decision making process.

@dims I think for the transition we will need an environment with 6 hosts. According to the pricing calculator, we estimate the monthly cost of $32k per month.

[dims]

@ameukam wow, that's quite a lot per year. especially if we add some head room (say 40k/month means close to half-a-million)

[dims]

@ameukam can you please check if there's something can be done from VMware side?

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[ameukam]

/remove-lifecycle rotten
/lifecycle frozen
/milestone clear

[ameukam]

Closing this in favor of #6877.

/close

[k8s-ci-robot]

@ameukam: Closing this issue.

In response to this:

Closing this in favor of #6877.

/close

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.