Skip to content

feat: add persistent storage options to k8s driver#3766

Merged
tonistiigi merged 1 commit intodocker:masterfrom
jsternberg:k8s-driver-statefulset
Apr 2, 2026
Merged

feat: add persistent storage options to k8s driver#3766
tonistiigi merged 1 commit intodocker:masterfrom
jsternberg:k8s-driver-statefulset

Conversation

@jsternberg
Copy link
Copy Markdown
Collaborator

@jsternberg jsternberg commented Mar 31, 2026

The k8s driver now supports the persistent-volume-claim.requests.storage option.
Setting this option changes the deployment into a statefulset and
creates a persistent volume claim where the buildkit data is stored.

Fixes #2056.
Replaces #2938.

@jsternberg
Copy link
Copy Markdown
Collaborator Author

@AkihiroSuda I was able to test this and it seems to work on my local k3s. Can you take a look at this and make sure it works for you and doesn't change any existing behavior? I don't use the kubernetes driver in my normal workload.

@jsternberg jsternberg marked this pull request as ready for review April 1, 2026 17:40
The k8s driver now supports the `persistent-volume-claim.requests.storage`
option. Setting this option changes the deployment into a statefulset
and creates a persistent volume claim where the buildkit data is stored.

Signed-off-by: Jonathan A. Sternberg <jonathan.sternberg@docker.com>
@jsternberg jsternberg force-pushed the k8s-driver-statefulset branch from bd58790 to 0a0fc90 Compare April 1, 2026 20:45
@jsternberg jsternberg requested a review from AkihiroSuda April 1, 2026 20:46
@tonistiigi tonistiigi merged commit 7b5d737 into docker:master Apr 2, 2026
160 checks passed
@jsternberg jsternberg deleted the k8s-driver-statefulset branch April 2, 2026 01:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Support statefulSets with the kubernetes driver

3 participants