Build
Managed Container registry on your own cluster
A container registry on your own cluster: builds push there, apps pull from there, and your images never go to a third-party registry.
Installed once per cluster and shared by every project on it.
A recent addition. It installs today, and the console marks it as new until it has run on a customer's cluster.
01What it does
Container registry, run for you
zot 2.1.18 on the vendor's chart, with every image and the build cache on one volume.
Once it reports healthy it becomes the default destination for every build on its cluster, ahead of your organization's default registry, and appears in the registry picker as Registry on your cluster's name. An app can still be pointed at another registry. Builds push with one credential and nodes pull with a second, read-only one, so nothing that can pull can overwrite the image an app is running. Both are generated on the cluster and kept there, never in Anyport's database.
Every build stores a new image and the build cache lives here too, so the disk is the whole cost: roughly 10Gi for a few apps, 50Gi for a dozen building often. Once a day it keeps the 10 most recent images of each app, which is also how far back you can roll back, and drops build cache older than 14 days. An image any app is running is never removed, and a rollback to one that was removed is refused rather than left to fail.
Its images stay on the cluster that built them: an app on another cluster cannot pull from it. Uninstalling it deletes every image it holds, so Anyport refuses while any app is still running one and names the apps to move first. Not offered on Anyport Cloud, where builds push with a registry credential instead.
02Options
What you choose
What the console asks when you create it, in the catalog's own numbers. Anything marked chosen once cannot change without creating a new instance.
- Scope
- Once per cluster
- Storage
- 20Gi by default, chosen once; roughly 10Gi for a few apps, 50Gi for a dozen building often
- Images kept
- 10 per app by default, which is also the rollback window
- Build cache
- Kept 14 days by default
- Credentials
- Separate push and read-only pull credentials, kept on the cluster
- Uninstall
- Deletes every image; refused while an app is running one
- Anyport Cloud
- Not offered
03Adding it
Add Container registry to a cluster
Cluster-scoped, so it is added from the cluster rather than from a project, once.
- 01Open the cluster and go to Services.
- 02Pick Container registry and choose its storage size. The size is fixed once installed, so size it for the images you expect to keep.
- 03Install it. Anyport installs it once for the cluster and generates its push and pull credentials there.
- 04Once it reports healthy, builds on the cluster push to it unless their app names another registry, and Anyport places the pull credential for the apps built there.