6 ms·
It is not immediately clear to me if the limit is per repo/package or globally in the hub. For instance, I fear it will not be possible to add a new kubernetes
by keisborg 2y ago
It is not immediately clear to me if the limit is per repo/package or globally in the hub. For instance, I fear it will not be possible to add a new kubernetes node to my cluster without hitting the limit as it would need to pull all the individual images.
- ragingroosevelt 2y agoWhy are you not using a registry mirror/cache (eg jfrog artifactory, etc)? Own your supply chain.
- RobotToaster 2y agoWhen that cache has to update it will make more than 10 pulls.
- keisborg 2y agoExactly this. And when a base image has a new release, all images based on this will also need an update
- davman 2y agoits globally in the hub. The announcement says they are rolling out the block in March but this already blew up my k8s clusters since last weekend. Have tried looking for an option to tell k8s to always use authentication tokens for image pulls, but can't find a way, going to have to add Kyverno to mutate all incoming Deployments to add imagePullSecrets.