Option to configure registry-mirrors for tenant clusters
What is the use case? I'd prefer to have a dedicated harbor instance in main cluster and configure all tenants cluster to pull all images through this main harbor BY DEFAULT... What do you think?
Sounds interesting, let's consider global option for this
Related issue: https://github.com/cozystack/cozystack/issues/173
What is the use case? I'd prefer to have a dedicated harbor instance in main cluster and configure all tenants cluster to pull all images through this main harbor BY DEFAULT... What do you think?
If cozystack is the cloud and you are a user of it, deploying something there, I would certainly not expect my docker images to be automagically pulled through some third-party cache owned by the administrators of cozystack. I'm quite sure that this use case is solved by appropriate cloudinit scripts, that's how we configured registry mirrors in AWS for our EKS nodes. WDYT?
Users can explicitly configure Cozystack to use Google Container Registry: https://cozystack.io/docs/operations/talos/configuration/talos-bootstrap/#preparation
registries:
mirrors:
docker.io:
endpoints:
- https://mirror.gcr.io
Hi, @kvaps. I'm Dosu, and I'm helping the cozystack team manage their backlog and am marking this issue as stale.
Issue Summary:
- You requested an option to configure registry-mirrors specifically for tenant clusters.
- A maintainer suggested using a dedicated harbor instance in the main cluster as a global default for tenant clusters.
- You found this global option interesting but noted other users prefer explicit configuration via cloudinit scripts.
- Another user highlighted that explicit registry mirror configuration is already possible in Cozystack.
- The issue remains unresolved with no recent updates.
Next Steps:
- Please let me know if this issue is still relevant to the latest version of Cozystack by commenting here.
- If I don’t hear back within 7 days, this issue will be automatically closed.
Thank you for your understanding and contribution!