Evaluate CDN Providers for artifacts distribution

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

Evaluate CDN Providers for artifacts distribution #3556

Closed ameukam closed 2 weeks ago

ameukam commented 2 years ago

Part of:

https://github.com/kubernetes/steering/issues/239

Scope of the GCP resources we want to use:

Projects	Tenants	Bucket name	Total Size	Object count	Estimated Traffic
k8s-artifacts-prod	Kubernetes	k8s-artifacts-prod	62.45 GiB	2136	38.6 TiB
k8s-release	Kubernetes	k8s-release	7.21 TiB	337481	Pending*
k8s-release	Kubernetes	k8s-release-dev	8.77 TiB	406370	Pending*

*data collection still in progress

/area artifacts

ameukam commented 2 years ago

cc @dims @cblecker

ameukam commented 2 years ago

/milestone v1.25

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:

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

ameukam commented 2 years ago

/remove-lifecycle stale

ameukam commented 2 years ago

/milestone v.126

k8s-ci-robot commented 2 years ago

@ameukam: The provided milestone is not valid for this repository. Milestones in this repository: [v1.24, v1.25, v1.26]

Use /milestone clear to clear the milestone.

In response to [this](https://github.com/kubernetes/k8s.io/issues/3556#issuecomment-1221128355): >/milestone v.126 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.

ameukam commented 2 years ago

/milestone v1.26

vielmetti commented 1 year ago

For reference, at Equinix Metal this s3.xlarge configuration https://metal.equinix.com/product/servers/s3-xlarge/ has 2x 10G network, and 2 x 960 GB SSD + 12 x 8 TB HDD storage, which would let the entirety of these artifacts fit on a single machine.

ameukam commented 1 year ago

/milestone v1.27

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:

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

ameukam commented 1 year ago

/remove-lifecycle stale

The SOW for Fastly is signed so we are ready to use it for dl.k8s.io.

ameukam commented 1 year ago

/milestone v1.28

ameukam commented 1 year ago

/milestone v1.29

dl.k8s.io is now shielded by Fastly but still using kubernetes-release as an origin. We should close when https://github.com/kubernetes/k8s.io/issues/2396 is done.

ameukam commented 9 months ago

/milestone v1.30

k8s-triage-robot commented 6 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

ameukam commented 6 months ago

/remove-lifecycle stale

ameukam commented 4 months ago

/milestone v1.31

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

ameukam commented 1 month ago

/remove-lifecycle stale

ameukam commented 2 weeks ago

Contract with Fastly is renewed for a longer term. We can close this.

/close

k8s-ci-robot commented 2 weeks ago

@ameukam: Closing this issue.

In response to [this](https://github.com/kubernetes/k8s.io/issues/3556#issuecomment-2301371260): >Contract with Fastly is renewed for a longer term. We can close this. > >/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.