Skip to main content

External Registry

ExternalRegistry​

Connection to a third-party artifact registry.

It creates the credentials and, for supported types, an Artifact Registry remote (pull-through) repository for sources such as Docker Hub or Quay.io. It does not host artifacts.

PropertyTypeDescription
apiVersionstringAPI schema version. Must be lowops.manifests.v1.
kindstringResource kind. Must be ExternalRegistry.
metadatamapThe engine reads the reserved keys name and organization to resolve the identity of the manifest.
specSpecExternal registry configuration. See Spec.

Spec​

External registry connection details.

Artifact format, base URL and authentication method.

PropertyTypeDescription
enabledboolNOT YET IMPLEMENTED. The engine ignores this field and always provisions the registry. Intended use: false leaves the registry out of the execution graph.
descriptionstringOptional description. For AR-backed types, the engine copies it to the Artifact Registry remote repository.
typestringArtifact format. One of DOCKER, HELM, MAVEN, NPM, PYTHON, GO, DART or BUF. BUF and DART use direct token authentication. All other types create an Artifact Registry remote (pull-through) repository.
urlstringBase URL of the external registry. Required. The engine uses it for artifact pulls and as the computed publish URL. For AR-backed types it also passes it to the remote repository. It must be a valid URI reference (RFC 3986). A scheme is optional: registries use bare hosts such as docker.io, and image references must not carry a scheme.
authenticationstringAuthentication method. One of bearer, token, ssh or basic. basic creates username and password secrets. The other methods create one credential secret. If unset, the engine creates no secrets (anonymous access).