Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Setting up storage space under CNCF/AWS account for pushing K8s Artifacts from registry.k8s.io to #3541

Closed
riaankleinhans opened this issue Mar 21, 2022 · 3 comments
Assignees

Comments

@riaankleinhans
Copy link
Contributor

We need input on best way to regionalize this storage cost-effectively so we can know where to implement the 302
Is there an agreed upon naming scheme?
For copies of container images we always use immutable tags (we only redirect blob requests… by design immutable)
We are just substituting the host currently
Do we have a bucket per region?
OR do we hand off to AWS at top level?
Should Cloudfront used? Ted can come in and advise

@riaankleinhans
Copy link
Contributor Author

/assign @jaypipes

@hh
Copy link
Member

hh commented Mar 31, 2022

Closing in favour of #3568
/close

@riaankleinhans riaankleinhans moved this from Backlog to Validation Done in registry.k8s.io (SIG K8S Infra) Mar 31, 2022
@k8s-ci-robot
Copy link
Contributor

@hh: Closing this issue.

In response to this:

Closing in favour of #3568
/close

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.

Repository owner moved this from Validation Done to Breakdown Done in registry.k8s.io (SIG K8S Infra) Mar 31, 2022
@hh hh moved this from Breakdown Done to Validation Done in registry.k8s.io (SIG K8S Infra) Apr 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

No branches or pull requests

4 participants