Freedom251 › Container Build Tools
kpack

What kpack is
kpack is a Kubernetes-native service for building OCI images with Cloud Native Buildpacks. Its declarative resources define build behavior: a builder sets the buildpack order and operating-system stack, while an image resource schedules builds and rebuilds after source code, buildpacks, or stacks change. A separate build resource runs a single build. Images are published to a configured tag, with additional tags limited to that same registry. Image resources support volume-based or registry-based caching, and Kubernetes secrets can provide credentials for publishing images and accessing private Git repositories. The build method is daemonless, with multiple cache backends. kpack is free and open source under the Apache-2.0 license, for API use in a self-hosted setup. Installation requires Kubernetes 1.22 or later, kubectl, cluster-admin permissions, and an accessible Docker V2 registry. SSH host key checking for Git credentials is disabled by default, though it can be enabled through a controller environment variable. Legacy Cloud Native Buildpacks service bindings are deprecated in kpack.io/v1alpha2 and are expected to be removed.
Who it suits
kpack suits teams building Cloud Native Buildpacks OCI images in a Kubernetes environment. It requires cluster-admin permissions and access to a Docker V2 registry, so it is for teams able to provide those prerequisites.
What it does well
- Automatically rebuilds images after relevant changes.
- Supports volume-based and registry-based caching.
- Kubernetes secrets can provide publishing credentials.
- Free and open source under Apache-2.0.
What to know first
- Requires Kubernetes 1.22 or later.
- Installation requires cluster-admin permissions.
- Additional image tags must use the configured registry.
- SSH host key checking is disabled by default.
Limits
The free plan requires a Kubernetes cluster, kubectl, cluster-admin permissions, and an accessible Docker V2 registry. Additional image tags must use the same registry as the configured image tag.
Plans
| Plan | Billed and limits | Price |
|---|---|---|
| Free / open source | Requires a Kubernetes cluster, kubectl, cluster-admin permissions, and an accessible Docker V2 registry | Free |
As github.com lists them, read 4 Oct 2026. The maker's own page has the final word.
Getting started
- Prepare Kubernetes 1.22 or later and kubectl.
- Obtain cluster-admin permissions and access to a Docker V2 registry.
- Install kpack using the project's GitHub site.
- Configure a builder resource with the buildpack order and operating system stack.
- Set up an image resource for scheduled builds, or a build resource for a one-off build.
- Provide registry or private Git credentials with Kubernetes secrets as needed.
Verdict
kpack provides declarative, daemonless image builds and automatic rebuilds within Kubernetes. Check the registry constraint and installation requirements before adopting it.
Questions
How much does kpack cost?
kpack is free and open source.
What license does kpack use?
The repository identifies its license as Apache-2.0.
What does kpack build?
It builds OCI images using Cloud Native Buildpacks.
Which platforms are listed?
The listed platforms are API and self-hosted.
Which registries and credentials can it use?
Kubernetes secrets can provide publishing credentials for Docker registries and access credentials for private Git repositories. Documentation examples cover Docker Hub and Google Container Registry, as well as GitHub credentials.
What are the installation requirements?
Installation requires Kubernetes 1.22 or later, kubectl, cluster-admin permissions, and an accessible Docker V2 registry.
Facts from kpack's own pages
- Automatic rebuilds
- Image resources schedule rebuilds when source code or builder buildpacks or stacks change. · github.com, 4 Oct 2026
- Builder configuration
- A declarative builder resource configures the buildpack order and operating system stack used for builds. · github.com, 4 Oct 2026
- Caching
- Image resources support volume-based or registry-based build caching. · github.com, 4 Oct 2026
- Credentials
- Kubernetes secrets can provide credentials for publishing images to Docker registries and accessing private Git repositories. · github.com, 4 Oct 2026
- Image registry
- Built OCI images are published to a configured image tag, and additional tags must use the same registry because cross-registry exporting is unsupported. · github.com, 4 Oct 2026
- Installation requirements
- Installation requires Kubernetes 1.22 or later, kubectl, cluster-admin permissions, and an accessible Docker V2 registry. · github.com, 4 Oct 2026
- Integrations
- The documentation includes examples for Docker Hub, Google Container Registry, and GitHub credentials. · github.com, 4 Oct 2026
- License
- The repository identifies its license as Apache-2.0. · github.com, 4 Oct 2026
- One-off builds
- A build resource can execute a single Cloud Native Buildpacks OCI image build. · github.com, 4 Oct 2026
- Purpose
- kpack is a Kubernetes native container build service that builds OCI images using Cloud Native Buildpacks. · github.com, 4 Oct 2026
- Security behavior
- SSH host key checking for Git credentials is disabled by default and can be enabled through a controller environment variable. · github.com, 4 Oct 2026
- Service bindings
- Legacy Cloud Native Buildpacks service bindings are deprecated in kpack.io/v1alpha2 and are expected to be removed; the docs direct users to Kubernetes Service Binding configuration. · github.com, 4 Oct 2026
- Support
- The project README points users to a weekly working group and the CNCF Slack community. · github.com, 4 Oct 2026
Where kpack stands on Freedom251
- Container Build Tools#20 of 34