search

kubernetes-retired / funding

Funding requests for project infrastructure, events, and consulting.
Apache License 2.0
16 stars 13 forks source link

request: recurring to fund Alibaba account for minikube #14

Closed RA489 closed 1 year ago

RA489 commented 4 years ago

Currently I don't have estimates but we do minikube testing in different clouds, gcloud, azure, but we don't have any testing in Alibaba.

Refs: https://github.com/kubernetes/minikube/issues/7695

RA489 commented 4 years ago

cc @medyagh

dims commented 4 years ago

@resouer @idvoretskyi Are there there any Alibaba credits available for community work?

idvoretskyi commented 4 years ago

@dims CNCF doesn't have any yet.

How much is needed (total budget)?

medyagh commented 4 years ago

@dims CNCF doesn't have any yet.

How much is needed (total budget)?

the estimate would depend on knowing how many downloads we get on traffic and how much it costs on alibaba. currently minikube has 3 million downloads on github, we could start with guess estimate $2000 a mohth and from then we try to adjust the price if the are more downloads at that time

dims commented 4 years ago

@medyagh so this is just for images then?

resouer commented 4 years ago

I am not aware of any form of funding from Alibaba Cloud side but the container image service of Alibaba Cloud is indeed free.

An alternative is to use this minikube fork (which is actively maintained): https://github.com/AliyunContainerService/minikube

medyagh commented 4 years ago

@dims @resouer it would be for both Docker image and also minikube binaries and preload tar files . so we need a storage bucket as well as image repository for the container

blueelvis commented 4 years ago

@resouer - That fork seems to be 398 commits and 1 release behind of what is currently on the main repo.

medyagh commented 3 years ago

@dims @resouer a gentle reminder about this issue.

idvoretskyi commented 3 years ago

@medyagh a rough estimate in $$$ is strongly likely still.

medyagh commented 3 years ago

@idvoretskyi we would like to start with $3000 a month estimate then if needed update it.

idvoretskyi commented 3 years ago

@dims FYI ^

medyagh commented 3 years ago

@idvoretskyi is there any updates on this ?

idvoretskyi commented 3 years ago

@medyagh I think we are waiting for approval and formal request from the steering, not from me.

dims commented 3 years ago

@idvoretskyi @medyagh i dropped the ball on this. apologies. will get a response from steering in a few days. Personally i'd be +1 on this.

idvoretskyi commented 3 years ago

@dims thanks!

liggitt commented 3 years ago

That amount seems reasonable to me, but I'd like to understand the intended use better.

it would be for both Docker image and also minikube binaries and preload tar files

the estimate would depend on knowing how many downloads we get on traffic and how much it costs on alibaba.

Is this for running CI to test in that environment, or would this attract production/external traffic? I'd like to understand the implications if the traffic and costs turn out to be higher than expected. Will you be able to control those by reducing frequency/quantity of test jobs, or will the traffic be outside the project's control?

dims commented 3 years ago

@medyagh can you please confirm/respond?

mrbobbytables commented 3 years ago

One other thought, as this would be community owned infrastructure, has wg-k8s-infra been engaged about the long term stewardship of it?

fejta-bot commented 3 years ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale

medyagh commented 3 years ago

That amount seems reasonable to me, but I'd like to understand the intended use better.

it would be for both Docker image and also minikube binaries and preload tar files

the estimate would depend on knowing how many downloads we get on traffic and how much it costs on alibaba.

Is this for running CI to test in that environment, or would this attract production/external traffic? I'd like to understand the implications if the traffic and costs turn out to be higher than expected. Will you be able to control those by reducing frequency/quantity of test jobs, or will the traffic be outside the project's control?

@liggitt @dims @mrbobbytables sorry for the late response somehow it got lost in my notifications, this would be for the production traffic and we will not have a control over how much people would download it. Currently our binaries are hosted by google cloud but chinnese users do not have access to GCS buckets due to national firewall

idvoretskyi commented 3 years ago

@medyagh this is on the CNCF side already, taking care of this.

RA489 commented 3 years ago

/remove-lifecycle stale

ljinging commented 3 years ago

@medyagh We have requested $5200 coupon for your Alibaba Cloud Account . You should be able to see it after you log in Alibaba Cloud. It's under alibabacloud.com -> log in -> Expenses -> User Center -> Coupons.

Except for the minikube binaries, we suggest you host the related docker image on Container Registry of Alibaba Cloud (ACR https://www.alibabacloud.com/product/container-registry). ACR personal edition is free of charge for million developers. We are looking forward to promoting the popularization of K8s together.

idvoretskyi commented 3 years ago

@ljinging I'm a bit confused - does the Alibaba Cloud Account exist? We're setting a CNCF-owned, should we cancel this process?

cc @dims

dims commented 3 years ago

@medyagh same question as @idvoretskyi , also please grant access to the account for @idvoretskyi if so, as we have CNCF taking care of all accounts.

k8s-triage-robot commented 3 years ago

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

This bot triages issues and PRs according to the following rules:

You can:

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

/lifecycle stale

RA489 commented 3 years ago

/remove-lifecycle stale

justaugustus commented 2 years ago

@idvoretskyi -- Do we know the current status of this?

idvoretskyi commented 2 years ago

@justaugustus pending still, but thanks for flagging.

justaugustus commented 2 years ago

@idvoretskyi -- Just wanted to check in on this one! /assign @justaugustus @idvoretskyi

idvoretskyi commented 2 years ago

@justaugustus the work in progress on this under the CNCF credits program, will keep us posted

justaugustus commented 2 years ago

@justaugustus the work in progress on this under the CNCF credits program, will keep us posted

@caniszczyk -- Can we get a commit date on either:

k8s-triage-robot commented 2 years ago

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

This bot triages issues and PRs according to the following rules:

You can:

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

/lifecycle stale

RA489 commented 2 years ago

/remove-lifecycle stale

k8s-triage-robot commented 2 years ago

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

This bot triages issues and PRs according to the following rules:

You can:

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

/lifecycle stale

k8s-triage-robot commented 1 year ago

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

This bot triages issues and PRs according to the following rules:

You can:

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

/lifecycle rotten

palnabarun commented 1 year ago

/remove-lifecycle rotten

k8s-triage-robot commented 1 year 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:

You can:

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

/lifecycle stale

mrbobbytables commented 1 year ago

This issue has been open for going on 2.5 years now. We can bump again with CNCF, but before we do is this something that is still desired?

k8s-triage-robot commented 1 year 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:

You can:

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

/lifecycle rotten

k8s-triage-robot commented 1 year ago

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

This bot triages issues according to the following rules:

You can:

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

/close not-planned

k8s-ci-robot commented 1 year ago

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to [this](https://github.com/kubernetes/funding/issues/14#issuecomment-1527708074): >The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. > >This bot triages 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: >- Reopen this issue with `/reopen` >- Mark this issue as fresh with `/remove-lifecycle rotten` >- Offer to help out with [Issue Triage][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close not-planned > >[1]: https://www.kubernetes.dev/docs/guide/issue-triage/ 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/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.