-
Notifications
You must be signed in to change notification settings - Fork 791
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
Mutate eks-prow-build-cluster
image pulls to use ECR
#4928
Comments
Is ECR pull-through cache useful here? I'm thinking we might need to switch to specifying hashes rather than tags to benefit. Not sure, haven't thought this through. |
I think this came up previously, but lost the thread. Unfortunately it's not because:
|
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale ECR now supports registry.k8s.io, we should revisit this. /assign |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
/unassign |
Can we look in to using Kyverno to mutate image pulls on the eks-prow-build-cluster?
It will be faster and cheaper to pull images from ECR than the staging GCR registries.
Good candidates for sync to ECR would would be
gcr.io/k8s-prow/*
gcr.io/k8s-staging-test-infra/*
gcr.io/k8s-staging-*/*
Kyverno would rewrite the image that the submitted from
gcr.io/k8s-staging-test-infra/kubekins-e2e:v20230222-b5208facd4-master
toACCOUNT_NUMBER.dkr.ecr.us-east-2.amazonaws.com/[REPO_NAME]/kubekins-e2e:v20230222-b5208facd4-master
We would also have a prowjob that syncs that ECR repo with images from the staging repos.
Sample Kyverno policy:
/cc @ameukam @xmudrii
The text was updated successfully, but these errors were encountered: