readystack/kubevip repository overview

⁠kube-vip

readystack/kubevip:v1.3.1-CE-ubuntu24.04-r1

Source, recipe and records

• Source and build recipe: https://readystack.dev/products/kubevip/recipe⁠
• Upstream source at this release's pinned commit (v1.3.1): https://github.com/kube-vip/kube-vip/tree/6da770eac1eed9409a9feaccda3d782c94424c24⁠
• Product page: https://readystack.dev/products/kubevip⁠
• Hermetic Build Kit for this release (free with an account): https://readystack.dev/products/kubevip⁠
• Release history (JSON): https://readystack.dev/api/releases/kubevip⁠
• Defect record: https://readystack.dev/defects.html?product=kubevip⁠
• Today's scan: https://readystack.dev/products/kubevip#pp-grade⁠
• Report an issue: https://github.com/ReadyStackFree/readystack/issues/new?template=bug.yml&product=kubevip⁠
• 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 https://github.com/kube-vip/kube-vip⁠ tag v1.3.1 (Apache-2.0), commit 6da770eac1eed9409a9feaccda3d782c94424c24, built clean-room from official upstream source by ReadyStack⁠.

⁠Who uses it and why

Who: Administrators of on-premises, edge and bare-metal Kubernetes clusters who need a highly available control-plane address.

Why: kube-vip gives a Kubernetes cluster a virtual IP address and load balancer for its control plane and for LoadBalancer Services, announced over ARP or BGP, without external load-balancing hardware or software.

Use case: A team runs Kubernetes on its own servers with several control-plane nodes. kube-vip holds one virtual address for the API server on the elected leader and moves it to another control-plane node when the leader fails, so the worker nodes and administrators keep using the same address.

About the upstream project, written from its own description: https://github.com/kube-vip/kube-vip⁠ · https://kube-vip.io/⁠

⁠What you get

Signature, user and attestations below were measured on the published digest sha256:41b46d3507cc51611b4033ae3e37703307d75f957c2fb49d1d6173a02d8994b6 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/kubevip⁠
• 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:41b46d3507cc51611b4033ae3e37703307d75f957c2fb49d1d6173a02d8994b6; verify with cosign verify --key https://readystack.dev/keys/cosign.pub readystack/kubevip:v1.3.1-CE-ubuntu24.04-r1.
• Attestations — An SPDX SBOM and SLSA v1 build provenance are attached to this digest.
• Runs as a non-root user (kubevip).
• Built from source by ReadyStack.

⁠Which tag should I pull?

This image follows the ReadyStack release-tag convention:

• The current release is v1.3.1-CE-ubuntu24.04-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/kubevip:v1.3.1-CE-ubuntu24.04-r1

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

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

⁠Deployment

A static pod on every control-plane node (/etc/kubernetes/manifests/kube-vip.yaml), written by kube-vip manifest pod and shipped in the Kubernetes VM stack's install bundle (install/network/kube-vip.yaml). The image's default user is the unprivileged kubevip (uid 999); the pod sets runAsUser: 0 and adds NET_ADMIN and NET_RAW, because kube-vip adds the address to the node's interface, sends ARP and reads the root-only kubeconfig. Started without those settings it cannot do either.

docker run --rm readystack/kubevip:v1.3.1-CE-ubuntu24.04-r1 version

Plain docker run only prints the version or a manifest (manifest pod --interface <if> --address <vip> --controlplane --arp --leaderElection); kube-vip itself runs as a static pod.

⁠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/kubevip⁠. A clean-room rebuild from this release's archive on an egress-blocked host reproduced its linux/amd64 digest sha256:74dd28c7b8af69cd7cf4684338b782d1fbf939a1dbfabeb1545d70b077cf934b on 2026-10-29.

— ReadyStack · readystack.dev