bedrock

Allow a new image publisher

The registry allowlist only admits images from known publishers. When you add a component whose images come from somewhere new, you have to add that publisher first, or its pods are refused.

#Before you begin

You need the full image reference you want to run, for example quay.io/example/tool:v1.2.3.

#Find the image digest

Every image in bedrock is pinned by digest. Get the digest of the multi-architecture index for your tag:

shell
docker buildx imagetools inspect quay.io/example/tool:v1.2.3

Copy the Digest: line and write the image as quay.io/example/tool:v1.2.3@sha256:<digest> in your manifest.

#Add the publisher

Open tenant-workload/kyverno/admission/registry-allowlist.yaml. It contains three policies with the same pattern: one for application namespaces, one for data namespaces and one for every namespace labelled bedrockctl.com/database: "true". The pattern has two groups:

  • single repositories, such as quay\\.io/kiwigrid/k8s-sidecar, for when you trust one image
  • whole organisations, such as quay\\.io/(prometheus|prometheus-operator|strimzi)/, for when you trust everything a publisher ships

Add your entry to the right group in all three policies, then run make check-allowlist, which fails if the three patterns are not identical. CI runs the same check. Prefer a single repository unless you really trust the whole organisation.

Images from Docker Hub without a registry name, like nats:2.14, are matched as docker.io/nats. The pattern accepts official images with or without library/, so docker.io/library/nats matches too.

#Test before you apply

Write a test pod using the new image and check it with the Kyverno CLI:

shell
kyverno apply tenant-workload/kyverno/admission/registry-allowlist.yaml --resource test-pod.yaml

Also test a pod with an image that should still be refused, such as nginx:1.27, and confirm it fails. A policy that passes everything looks the same as a working one until you test the negative case.

#Apply it

shell
kubectl apply -f tenant-workload/kyverno/admission/registry-allowlist.yaml

The change affects new pods only. Running pods are not evicted.