readystack/virtoperator repository overview

⁠virt-operator

readystack/virtoperator:v1.9.1-CE-debian12-r1

Source, recipe and records

• Source and build recipe: https://readystack.dev/products/virtoperator/recipe⁠
• Upstream source at this release's pinned commit (v1.9.1): https://github.com/kubevirt/kubevirt/tree/c3d19093f9c7b843b3879b18dc088911c081c39e⁠
• Product page: https://readystack.dev/products/virtoperator⁠
• Hermetic Build Kit for this release (free with an account): https://readystack.dev/products/virtoperator⁠
• Release history (JSON): https://readystack.dev/api/releases/virtoperator⁠
• Defect record: https://readystack.dev/defects.html?product=virtoperator⁠
• Today's scan: https://readystack.dev/products/virtoperator#pp-grade⁠
• Report an issue: https://github.com/ReadyStackFree/readystack/issues/new?template=bug.yml&product=virtoperator⁠
• Signing key (cosign): https://readystack.dev/keys/cosign.pub⁠
• Part of the Kubernetes VM Stack: https://readystack.dev/stacks/kubernetes-vm-stack⁠

A cosign-signed build of KubeVirt v1.9.1 (github.com/kubevirt/kubevirt, commit c3d19093f9c7), Apache-2.0, built clean-room from official upstream source by ReadyStack⁠.

⁠Who uses it and why

Who: Kubernetes cluster administrators who run virtual machines in their clusters with KubeVirt.

Why: virt-operator installs KubeVirt and manages the lifecycle of its core components: it deploys them when a KubeVirt resource is created and rolls out new versions when that resource or the operator is updated.

Use case: An administrator adds virtual machine support to a cluster by applying the operator and then a KubeVirt resource, and virt-operator deploys the rest of KubeVirt. Later, an upgrade is a change to that resource, and virt-operator rolls out the new version while existing virtual machines keep running.

About the upstream project, written from its own description: https://kubevirt.io/user-guide/cluster_admin/installation/⁠ · https://kubevirt.io/user-guide/cluster_admin/updating_and_deletion/⁠ · https://github.com/kubevirt/kubevirt/blob/main/docs/components.md⁠

⁠What you get

Signature, user and attestations below were measured on the published digest sha256:55aee39b1c7b4a718b56226fee362727e9dd124f5b83ed23bf0b85a3c0986ed7 on 2026-10-29.

• Scan scores — we scan every image we publish every day (an SBOM made with syft, vulnerabilities matched with grype, scored with cerodeo-v1, the rubric ce.rodeo published until 2026-10-26) and record each scan with how its score was derived. This release's first and latest scan: https://readystack.dev/products/virtoperator⁠
• ReadyStack release check — passed at release on 2026-10-29: no fixable critical or high vulnerability (Docker Scout and OSV), a non-root user, SBOM and provenance attached. This is ReadyStack's own test, not a Docker grade; vulnerabilities published since then are in today's result at https://readystack.dev/queue⁠.
• Signed — cosign signature by the ReadyStack release key (fingerprint 04daa92344a52dbc) on this release's index digest sha256:55aee39b1c7b4a718b56226fee362727e9dd124f5b83ed23bf0b85a3c0986ed7; verify with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/virtoperator:v1.9.1-CE-debian12-r1.
• Attestations — An SPDX SBOM and SLSA v1 build provenance are attached to this digest.
• Runs as a non-root user (1001).
• Built from source by ReadyStack.

⁠Which tag should I pull?

This image follows the ReadyStack release-tag convention:

• The current release is v1.9.1-CE-debian12-r1 — the release listed at readystack.dev. Release tags use the pattern <upstream-version>-CE-<base-os>-r<N>; the current one is signed, attested (SBOM + provenance), and is provided under the ReadyStack Agreement⁠.

• Earlier release tags (an older version or revision in the same pattern) are superseded. They stay pullable so existing deployments can pin them, but they are no longer re-graded, and fixes appear only in newer releases: move to the current release. For a superseded release's build kit, ask support.

• Release tags never move, so pulling the same tag again never changes the image. To be offered each new release automatically (a new revision r<N+1>, or a new upstream version), use the ReadyStack Renovate preset: https://readystack.dev/updates.html⁠

• Any tag beginning with internal- is an engineering-pipeline artifact published for build observability. It is unsupported, may change or disappear without notice, and must not be used in production.

# ✓ current release
docker pull readystack/virtoperator:v1.9.1-CE-debian12-r1

# ✗ unsupported (do not pull)
docker pull readystack/virtoperator:internal-...

This release is signed; verify it with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/virtoperator:v1.9.1-CE-debian12-r1 (the signature is recorded in the public Sigstore transparency log). Support: [email protected]⁠, as set out in the ReadyStack Agreement⁠.

⁠Deployment

virt-operator installs, configures and upgrades KubeVirt: it reads the KubeVirt custom resource and deploys virt-api, virt-controller, virt-exportproxy and virt-handler (with the images named in its environment), and keeps them at the declared version.

This image runs only inside a Kubernetes cluster, started by its stack's manifests (the admin guide shows how); started on its own it exits. Its one-run check, which VERIFY_OFFLINE.sh also runs: docker run --rm --network none readystack/virtoperator:v1.9.1-CE-debian12-r1 --help prints --dump-install-strategy.

⁠The full ReadyStack Hermetic Build Kit

The complete --network=none build kit for this image — plus admin/DB/API handbooks, the build's validation records, and its build provenance records — is a free download for any registered account at readystack.dev/products/virtoperator⁠. A clean-room rebuild from this release's archive on an egress-blocked host reproduced its linux/amd64 digest sha256:78de21c348d6b5c03db14e9b14e4fe02f947114771f8897f53c2f52bf435a0a6 on 2026-10-29.

— ReadyStack · readystack.dev