aws: Add support for using ECR as pull-through image cache#16593
aws: Add support for using ECR as pull-through image cache#16593k8s-ci-robot merged 1 commit intokubernetes:masterfrom
Conversation
|
Hi @rsafonseca. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions 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-sigs/prow repository. |
|
/ok-to-test |
|
Any idea why these e2e tests might be failing @hakman? could something be leaking somewhere? or do you think there's any change here that could be somehow related to this weird behaviour? EDIT: nvm, found the problem... hidden tabs in string literal.. damn vscode 😂 |
|
Please ignore the IPv6 tests |
|
All good then, though it looks like pull-kops-e2e-cni-cilium-eni is flaky, passed on retest. |
a77071a to
a7dbaac
Compare
45e0800 to
f682340
Compare
615a93f to
a7dbaac
Compare
|
Any update about this PR? Do you need any help or test, to be merged faster? |
|
Did you get a chance to review this yet @hakman @johngmyers ? :) |
|
The tests are broken, so please ignore for now. Will fix them and merge this. |
|
/lgtm |
|
/hold for tests to be fixed |
Signed-off-by: Rafael da Fonseca <rafael.fonseca@wildlifestudios.com>
808f9b5 to
1794614
Compare
|
/lgtm |
|
/unhold |
|
/test all |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: hakman The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/retest |
|
@rsafonseca: The following tests failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. DetailsInstructions 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-sigs/prow repository. I understand the commands that are listed here. |
|
/override pull-kops-e2e-cni-amazonvpc |
|
@hakman: Overrode contexts on behalf of hakman: pull-kops-e2e-cni-amazonvpc DetailsIn response to this:
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-sigs/prow repository. |
|
/override pull-kops-e2e-k8s-gce-ipalias |
|
@hakman: Overrode contexts on behalf of hakman: pull-kops-e2e-k8s-gce-ipalias DetailsIn response to this:
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-sigs/prow repository. |
|
/override pull-kops-e2e-cni-cilium-eni |
|
@hakman: Overrode contexts on behalf of hakman: pull-kops-e2e-cni-cilium-eni DetailsIn response to this:
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-sigs/prow repository. |
This PR introduces a simple way to enable using ECR as a Pull-through image cache, without having to mutate images on the cluster using tools like Kyverno.
Containerd already has support for specifying registry mirrors in kops, but since ECR uses short lived tokens, it's not trivial (or even impossible without adding a few extra hacks on top of it) to use it as a pull-through cache.
This PR also bumps the ecr-credential-provider binary, which before version 1.29.0 specifically tried to parse an ECR repo URL from the image passed, leading to not being possible to enable this feature. This is now resolved in the latest versions.
This PR uses a flag to enable the feature when needed, and adds any server addresses configured in the mirrors to be allowed on the CredentialProviderConfig object that kops configures on the kubelet.
To configure this:
example: