Overcome public registry limitations
This documents the in-development version. Switch to v2.3 for the latest stable release.
This documentation will help you configure Kuik in order to overcome public registry limitations.
Best suited for
Section titled “Best suited for”- You face an image pull rate limit
- Your upstream registry is no longer available
- Your images are already pushed to multiple registries, or you let kuik copy them there with an ImageMirror
Benefits
Section titled “Benefits”Your Kubernetes cluster will seamlessly pull images from another registry and avoid listed difficulties.
kuik itself stays within the quota: it reads each registry at the pace you configure, and one request serves every monitor and mirror tracking the same image. See Registry pacing.
Implementation
Section titled “Implementation”Kuik custom resource to use
Section titled “Kuik custom resource to use”TODO
Configuration example
Section titled “Configuration example”TODO