Enable Registry Cache Extension [KIM/feature]

kyma-project / infrastructure-manager

Apache License 2.0

0 stars 10 forks source link

Enable Registry Cache Extension [KIM/feature] #135

Open pbochynski opened 7 months ago

pbochynski commented 7 months ago

Description It is possible now to run docker registry cache in Gardener cluster. The new feature is described here: https://github.com/gardener/gardener-extension-registry-cache/blob/main/docs/usage/registry-cache/configuration.md Provide a way to enable and configure registry in the shoot cluster as our customers do not have access to the shoot spec to do that on their own.

Reasons Local registry cache can decrease cost of traffic from docker registry. It also can be a solution for the docker registries that are not designed to support high load with guaranteed high availability (Artifactory).

tobiscr commented 4 months ago

@pbochynski : quick questions regarding this feature:

How far should we allow customers to configure this image cache (just enable/disable cache, edit the list of cached registries)?
Would it make sense to enable this feature always with meaningful default values? We could configure it to cache per default everything from Kyma-registries, SAP Artifactory, Dockerhub, Quay.io etc

pbochynski commented 4 months ago

You need to configure the registry and sometimes also credentials to access the registry. Remember that physically each registry is a new cache. In the case of Artifactory, each repository is technically a new registry. If you want to configure 5 repositories in Artifactory you will end up with 5 instances of registry cache.

tobiscr commented 3 weeks ago

Screenshot 2024-08-26 at 14 55 07

pbochynski commented 2 weeks ago

I checked it and RegistryConfig is not available in the shoot cluster. The only way to configure the cache is by adding the extension to the shoot spec. I created an issue and I will discuss it with the Gardener team on Thursday (29.08.2024).