SKS: Container registry mirroring for Karpenter nodes

Exoscale SKS now supports configuring OCI registry mirrors for nodes provisioned by Karpenter. Registry mirror endpoints and pull credentials can be defined in an ExoscaleNodeClass and applied consistently to new nodes created from that class.

What this enables

• Faster and more reliable image pulls: Route image requests through private mirrors located closer to your workloads.
• Lower egress costs: Reduce repeated downloads from public registries by caching commonly used container images.
• Fewer upstream limits: Avoid relying solely on public registries and reduce the impact of their rate limits or availability issues.
• Greater supply-chain control: Use private registries, authenticated mirrors, and trusted TLS configurations for container images.

Why it matters

Registry mirroring gives teams more control over how container images reach their SKS clusters. It improves reliability and supports production environments that require private access, predictable image delivery, or tighter control over external dependencies.

Learn how to configure OCI registry mirroring for Karpenter nodes.