Investigate usage of VMC for CAPV tests

kubernetes / k8s.io

Code and configuration to manage Kubernetes project infrastructure, including various *.k8s.io sites

https://git.k8s.io/community/sig-k8s-infra

Apache License 2.0

713 stars 794 forks source link

Investigate usage of VMC for CAPV tests #5864

Closed ameukam closed 2 weeks ago

ameukam commented 11 months ago

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 :

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

ameukam commented 11 months ago

cc @sbueringer @chrischdi @killianmuldoon @fabriziopandini

ameukam commented 11 months ago

cc @dims

dims commented 11 months ago

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

chrischdi commented 11 months ago

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

sbueringer commented 11 months ago

Also image-builder

ameukam commented 11 months ago

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 commented 11 months ago

@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 commented 11 months ago

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

k8s-triage-robot commented 7 months ago

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 commented 6 months ago

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 commented 6 months ago

/remove-lifecycle rotten /lifecycle frozen /milestone clear

ameukam commented 2 weeks ago

Closing this in favor of https://github.com/kubernetes/k8s.io/issues/6877.

/close

k8s-ci-robot commented 2 weeks ago

@ameukam: Closing this issue.

In response to [this](https://github.com/kubernetes/k8s.io/issues/5864#issuecomment-2301336123): >Closing this in favor of https://github.com/kubernetes/k8s.io/issues/6877. > >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository.