Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Investigate usage of VMC for CAPV tests #5864

Closed
ameukam opened this issue Sep 18, 2023 · 13 comments
Closed

Investigate usage of VMC for CAPV tests #5864

ameukam opened this issue Sep 18, 2023 · 13 comments
Labels
area/infra/aws Issues or PRs related to Kubernetes AWS infrastructure lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. sig/k8s-infra Categorizes an issue or PR as relevant to SIG K8s Infra.

Comments

@ameukam
Copy link
Member

ameukam commented Sep 18, 2023

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 ameukam added the sig/k8s-infra Categorizes an issue or PR as relevant to SIG K8s Infra. label Sep 18, 2023
@k8s-ci-robot k8s-ci-robot added the sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. label Sep 18, 2023
@k8s-ci-robot k8s-ci-robot added this to the v1.29 milestone Sep 18, 2023
@k8s-ci-robot k8s-ci-robot added area/infra/aws Issues or PRs related to Kubernetes AWS infrastructure priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. labels Sep 18, 2023
@ameukam
Copy link
Member Author

ameukam commented Sep 18, 2023

@ameukam
Copy link
Member Author

ameukam commented Sep 18, 2023

cc @dims

@dims
Copy link
Member

dims commented Sep 18, 2023

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

@chrischdi
Copy link
Member

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

@sbueringer
Copy link
Member

Also image-builder

@ameukam
Copy link
Member Author

ameukam commented Sep 20, 2023

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
Copy link
Member

dims commented Sep 20, 2023

@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
Copy link
Member

dims commented Sep 20, 2023

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

@k8s-triage-robot
Copy link

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-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 28, 2024
@k8s-triage-robot
Copy link

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

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Feb 27, 2024
@ameukam
Copy link
Member Author

ameukam commented Feb 27, 2024

/remove-lifecycle rotten
/lifecycle frozen
/milestone clear

@k8s-ci-robot k8s-ci-robot removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Feb 27, 2024
@k8s-ci-robot k8s-ci-robot removed this from the v1.29 milestone Feb 27, 2024
@k8s-ci-robot k8s-ci-robot added the lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. label Feb 27, 2024
@ameukam ameukam removed the priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. label Feb 27, 2024
@ameukam
Copy link
Member Author

ameukam commented Aug 21, 2024

Closing this in favor of #6877.

/close

@k8s-ci-robot
Copy link
Contributor

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/infra/aws Issues or PRs related to Kubernetes AWS infrastructure lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. sig/k8s-infra Categorizes an issue or PR as relevant to SIG K8s Infra.
Projects
Status: Done
Development

No branches or pull requests

6 participants