Skip to content

Conversation

jetersen
Copy link

@jetersen jetersen commented Jan 19, 2025

Since AWS has added more options for pull through cache on ECR.

I would prefer to use that but there a still unsupported image sources. Not all registries are supported so this provides the flexibility to skip the once ECR Pull through cache handles.

There is still a benefit to k8s-image-swapper since it supports the image swap on a pod level. Cause we want use tooling to detect changes to the images we use on a higher level than the pod.

Currently ECR supports:

  • public.ecr.aws
  • registry-1.docker.io
  • registry.k8s.io
  • quay.io
  • ghcr.io
  • *.azurecr.io
  • registry.gitlab.com

So far we have come across other image sources we use that are not supported by ECR pull through:

  • registry.opensource.zalan.do
  • us-docker.pkg.dev
  • xpkg.upbound.io

image
image

@jetersen
Copy link
Author

@estahn not sure what your notification settings are so, I'll allow myself to ping you 😅

@jetersen
Copy link
Author

Been running this in production for a while and works as intended.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant