Skip to content

Images

Public images

Images of the public registries (docker.io, ghcr.io, quay.io, registry.k8s.io) are pulled as usual, by their usual names: the cluster's registry caches them, transparently. Pin them by digest (image@sha256:…) or by an exact tag.

The cluster's registry

registry.ethere.internal holds the images built for this cluster. The nodes pull from it with their own credentials: a pod references registry.ethere.internal/<repository>:<tag> (or @sha256:…), with no imagePullSecrets.

Pushing

registry.cloud.dampetra.com is the same registry for people and CI: the same images, served to the outside, behind a sign-in. Its repositories are given to groups of the identity provider (a project's group: its repositories under its prefix, <project>/…); ask an admin, as for a namespace.

  1. Sign in on https://registry.cloud.dampetra.com (the cluster's identity provider, as for kubectl).
  2. Create an API key there (the user menu, API Keys): a CI gets its own, revocable.
  3. Log in with it, your email as the user name:

    docker login registry.cloud.dampetra.com -u <email>   # the key as the password
    docker push registry.cloud.dampetra.com/<project>/<image>:<tag>
    

    (podman, buildah, crane, regctl, oras alike.)

The pods reference the pushed image by the cluster's name, registry.ethere.internal/<project>/<image>:<tag>, still without imagePullSecrets. Nothing is public: no anonymous pull, a group sees only its repositories.

A registry of the project's own

A private registry elsewhere works with an imagePullSecrets of the namespace (a kubernetes.io/dockerconfigjson Secret). Pulls are made by the nodes, not the pods: no network policy is needed for them.

Versions

Deploy a precise version: a tag never reused (a commit's hash, a release number) or a digest, written in the release's values (Deploying). latest and moving tags make a deployment depend on when a node pulled.