request: recurring to fund Alibaba account for minikube

[RA489]

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: kubernetes/minikube#7695

[RA489]

cc @medyagh

[dims]

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

[idvoretskyi]

@dims CNCF doesn't have any yet.

How much is needed (total budget)?

[medyagh]

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

@medyagh so this is just for images then?

[resouer]

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]

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

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

[medyagh]

@dims @resouer a gentle reminder about this issue.

[idvoretskyi]

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

[medyagh]

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

[idvoretskyi]

@dims FYI ^

[medyagh]

@idvoretskyi is there any updates on this ?

[idvoretskyi]

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

[dims]

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

@dims thanks!

[liggitt]

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]

@medyagh can you please confirm/respond?

[mrbobbytables]

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]

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]

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]

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

[RA489]

/remove-lifecycle stale

[ljinging]

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

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

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

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:

• 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 or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

[justaugustus]

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

[idvoretskyi]

@justaugustus pending still, but thanks for flagging.

[justaugustus]

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

[idvoretskyi]

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

[justaugustus]

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

• funding this via Cloud Credits
• directly funding for Alibaba

[k8s-triage-robot]

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:

• 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 or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

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

/lifecycle stale

[RA489]

/remove-lifecycle stale

[k8s-triage-robot]

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:

• 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 or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR 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 and PRs.

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

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

/lifecycle rotten

[palnabarun]

/remove-lifecycle rotten

[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

[mrbobbytables]

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]

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-triage-robot]

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

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

/close not-planned

[k8s-ci-robot]

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

In response to this:

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

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

/close not-planned

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.