Closed ameukam closed 1 year ago
/sig k8s-infra /committee steering
/assign @dims AS SIG k8s-infra chair
/cc
we talked about this in the sig-k8s-infra meeting as well. essentially Arnaud will update the request here to reflect that one of us (probably me) will fill the form with say fastly and explore what they offer, how this works and what they want in return as well.
I still don't know exactly what is offered in terms of features in the various Open Source programs. The request is made in order to engage in conversation with at least one service provider (possibly Fastly due to the partnership with the LF) to identify and clarify the technical requirements/constraints before engaging.
👀 👀 👀 @kubernetes/release-engineering
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:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
Still in progress.
/remove-lifecycle stale
@kubernetes/steering-committee Arnaud (@ameukam) has been able to get good results from the proof-of-concept in https://github.com/kubernetes/k8s.io/issues/3596 . So i will open up a service desk ticket that will help us rope in @caniszczyk and others from CNCF to talk to CloudFlare
This is back in @kubernetes/steering-committee court @ameukam
Amye Scavarda Perrin
Today 1:45 PM
So our preference for things like this is to have the projects reach out directly to the provider, and involve us if there needs to be some sort of zero-balance account billing.
Here, it looks like Cloudflare just needs an email to [os-sponsorship@cloudflare.com](mailto:os-sponsorship@cloudflare.com) with a link to the project’s landing page, repo, and a description of what engineering tools or resources your project provides to the developer community.
Can the steering committee run with that? It makes it a lot easier if you all run into issues down the road because they have a primary contact within the project.
If not, we can work out a way to connect with them, it’s just easier to have the project start the process.
This is back in @kubernetes/steering-committee court @ameukam
Amye Scavarda Perrin Today 1:45 PM So our preference for things like this is to have the projects reach out directly to the provider, and involve us if there needs to be some sort of zero-balance account billing. Here, it looks like Cloudflare just needs an email to [os-sponsorship@cloudflare.com](mailto:os-sponsorship@cloudflare.com) with a link to the project’s landing page, repo, and a description of what engineering tools or resources your project provides to the developer community. Can the steering committee run with that? It makes it a lot easier if you all run into issues down the road because they have a primary contact within the project. If not, we can work out a way to connect with them, it’s just easier to have the project start the process.
@dims With the probability that we may be listed in https://developers.cloudflare.com/sponsorships/, can you check with CNCF if there is any concern about Trademark logo ?
@ameukam yep will ask.
@ameukam no concerns about us getting listed there on that url.
Showing up here re the Equinix Metal open source program, as referenced in the discussion from the 2022-11-09 sig-k8s-infra meeting.
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.
This bot triages PRs according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the PR is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
/lifecycle frozen
We are in fastly's CDN program now, announcements pending.
Problem Statement
The Kubernetes project produces and distributes various artifacts used by the community. Currently system packages and binaries are hosted on Google's infrastructure. They should be hosted within community infrastructure that primarily rely on a cloud computing provider. Once the migration of those artifacts is done, we may face some issues (we faced the same issues with the migration k8s.gcr.io) :
Proposed Solution
I would like to propose we use a CDN provider for distribution. The proposal is not new; it's already done by many Open source projects for a long time now:
Cost
The cost is supposed to be supported by the plan we apply for but we still need to look at the details of those different plans.
Open Questions
Next Steps
EDIT: I don't think I can apply to for example The Fastly program on the behalf of the community so I would like one of SC members to apply to it.