registry.k8s.io
registry.k8s.io copied to clipboard
kubernetes
Explore Using CloudFront
We've mentioned this previously but had been focused on serving in-AWS clients with local copies and have not had much time since then.
We think the many-s3-buckets approach is working pretty well, particularly for "we will inspect client IP and route clients to their own AWS region if possible", but we should be exploring CloudFront as well for future optimization, particularly it seems for cloud-external traffic.
NOTE: This needs to wait until after the Code Freeze #181 , but going ahead and filing this so we're tracking.
cc @ameukam @rothgar
This should not require any notable code changes here, but tracking here for visibility. Configs for this would be in the kubernetes/k8s.io repo.
/kind feature /sig k8s-infra
@ameukam: The label(s) area/infra, area/infra/aws cannot be applied, because the repository doesn't have them.
In response to this:
/priority backlog /area infra /area infra/aws /milestone v1.28
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.
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
A Cloudfront distribution is used for 3 regions:
- asia-east1
- europe-west1
- europe-west4
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