k8s.io
k8s.io copied to clipboard
kubernetes
Evaluate CDN Providers for artifacts distribution
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
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/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas 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: 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:
/milestone v.126
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.
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.
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/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas 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
/remove-lifecycle stale
The SOW for Fastly is signed so we are ready to use it for dl.k8s.io.
/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.
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/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas 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
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/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas 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