Copy images to AWS regions

[jaypipes]

image-promoter needs the ability to copy to AWS regions, based on a per-region bucket scheme.

Related: kubernetes/registry.k8s.io#39

@jaypipes coordinating with @Verolop and @puerco from Release Engineering

[jaypipes]

/assign @jaypipes

[BenTheElder]

xref: https://kubernetes.slack.com/archives/CCK68P2Q2/p1649978570481889?thread_ts=1649976555.356029&cid=CCK68P2Q2

So the layout is like $bucket/containers/image/sha256:$blobhash for all the blobs in GCS.

@ameukam has already run a sync between the GCS behind k8s.gcr.io and an s3 bucket.

If we can have the promoter promote digests in the manifest to paths like this in a bucket, then once that's enabled for a bucket we just need to run a backfill sync once, and we don't need any code for the backfill, it's just gsutil rsync gs://us.k8s-artifacts-prod s3://$bucket.

This is also pretty easy to redirect to in oci-proxy statelessly.

[k8s-triage-robot]

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

[riaankleinhans]

/remove-lifecycle stale

@BenTheElder should we keep this open to drive changes to the promotor to push to the S3 buckets or would the process of periodic syncing the bucket with GCS be sufficient?

[riaankleinhans]

Resolved by kubernetes/k8s.io#4118
/close

[k8s-ci-robot]

@Riaankl: Closing this issue.

In response to this:

Resolved by kubernetes/k8s.io#4118
/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.