Files

1 line
3.1 KiB
JSON

{"text":["Container Registry","Hanzo Registry","A private registry for your container images at oci.hanzo.ai. It serves the OCI distribution API, so docker, podman, buildkit, skopeo and crane already know how to talk to it — and the credential is a short-lived token minted by your Hanzo IAM login, not a password living in a dockerconfigjson secret.","View Source","Registry","— Hanzo","Projects","Environments","Builds","Releases","Pipelines","gateway","Ready","payments-api","checkout-web","Building","docs-site","The service the session above is changing.","api.hanzo.ai","/v1/registry","Open in the console","Example project. Every name in it is one you would give your own.","Paste and ship","Paste this into any agent. It reads the skill manifest and calls Registry from there.","Agent prompt","api","Copy","Read https://hanzo.ai/skill.md and use Hanzo Registry in my project. Start with: hanzo registry images","Built on Hanzo IAM","The credential expires on its own, so there is nothing to rotate and nothing to leak","01","IAM Token Auth","An unauthenticated pull gets a 401 naming Hanzo IAM. Your client fetches a token there, the registry checks its signature against a certificate it holds, and the push goes through. No password is stored at either end.","02","Org-Scoped Repos","A repository name begins with your org, and what a token may do with it is decided by IAM at the moment the token is minted. Adding a teammate is one grant in one place, not a secret copied into a second.","03","Cosign + Attestation","cosign signatures and in-toto attestations are ordinary OCI artifacts, so they push and pull to the same repository as the image they describe. Verification happens where the image runs, against exactly what the registry stored.","04","OCI Compliant","The registry HTTP API v2 at /v2/, and nothing bespoke on top of it. Every client, scanner and admission controller that reads an image already speaks it, which is the whole point of not inventing one.","05","Tags come off cleanly","Deletes are enabled, so a tag you pushed by mistake goes away and the blobs behind it are reclaimed. A registry you can only add to is one that only grows.","06","The same account as everything else","Whoever signs into Hanzo Cloud is who pushes an image. One directory of people, one place to revoke someone — and no separate registry account to remember when they leave.","Delete the dockerconfigjson secret","Put a token IAM mints in its place, and let it expire on its own. There is nothing left to rotate.","terminal","hanzo","login oci.hanzo.ai","# IAM mints a short-lived token","docker push","oci.hanzo.ai/acme/api:v1.2.3","Quickstart","About IAM","Get started with Registry","View on GitHub","Related capabilities","The deploy unit","Dev, staging, prod — isolated","Source to signed image","Get Registry","OCI image registry","Apache-2.0","License:","hanzoai","Deploy to Cloud"],"links":["https://github.com/hanzoai","/cloud/projects","/cloud/environments","/cloud/builds","/registry","/cloud/releases","/cloud/pipelines","https://hanzo.team/","https://docs.hanzo.ai/docs/openapi/registry/","/iam","https://platform.hanzo.ai/deploy"]}