Page last updated:
Release Date: June, 26, 2020
0.2.0 represents a Beta release of the Tanzu Build Service.
pb cli has been deprecated in favor of the
kp cli for interacting with Tanzu Build Service. The
kp cli will be shipped with Tanzu Build Service in place of
pb. For more details see Using Tanzu Build Service.
Notable improvements in the
kpcli is more interoperable with
kpoutput is formatted to look consistent with
kpdoes not utilize a alternative YAML format used to apply kpack resources. Instead,
kpprovides imperative commands to interact with Tanzu Build Service.
pbrequired users to provide image tags when managing images,
kpuses image resource names for easier control.
kpcommands are configurable to work on a kubernetes namespace with a
- The ability to update images with
kp patch. This can be naturally used in a CI/CD context.
kp image createand
kp image patchwhich will tail build logs and wait for corresponding builds to complete.
- The ability to manage multiple stores and stacks.
- Improved output for
kp store statusto view available buildpacks.
Tanzu Build Service 0.2.0 now ships with four stacks. Output from
kp stack list:
NAME READY ID base True io.buildpacks.stacks.bionic default True org.cloudfoundry.stacks.cflinuxfs3 full True org.cloudfoundry.stacks.cflinuxfs3 tiny True io.paketo.stacks.tiny
The stacks are used in Custom Cluster Builders. The
default stack is installed and will be used when a stack is not selected for a builder, but the stack image is the same as the
For more details on stacks, see Managing Stacks.
Same with the new stacks, Tanzu Build Service 0.2.0 now ships with four Custom Cluster Builders. Output from
kp custom-cluster-builder list:
NAME READY STACK IMAGE base true io.buildpacks.stacks.bionic my-registry.io/ccb:base@sha256:abc123 default true org.cloudfoundry.stacks.cflinuxfs3 my-registry.io/ccb:default@sha256:abc123 full true org.cloudfoundry.stacks.cflinuxfs3 my-registry.io/ccb:full@sha256:abc123 tiny true io.paketo.stacks.tiny my-registry.io/ccb:tiny@sha256:abc123
Builders are used when creating images and can apply to different app use cases. The
default Custom Cluster Builder is used when a builder is not selected for an image but is installed with the same buildpacks and stack as the
For more details on builders, see Managing Builders.
Buildpack IDs have changed:
All of the previous
org.cloudfoundry.* ids are now
All of the previous
io.pivotal.* ids are now
- Projects are now completely optional. Build Service Cluster Builder secrets will be provided to any namespace that creates a Build Service image.
- Images can configure Cloud Native Buildpack Service Bindings.
Tanzu Build Service 0.2.0 ships with the following components:
Tanzu Build Service 0.2.0 ships with the following buildpacks:
- Tanzu Java
- Paketo NodeJS
- Paketo .NET Core
- Paketo Golang
- Paketo PHP
- Paketo HTTPD
- Paketo NGINX
- Paketo Procfile
Tanzu Build Service 0.2.0 ships with the following stacks:
Updates to the buildpacks and stacks are provided in the VMware Tanzu Build Service Dependencies.
Build Service can be installed on any Kubernetes cluster (v1.15 or later).
- Tanzu Build Service now requires Kubernetes api v1.15 or later
pbcli is deprecated,
kpcli should be used
- All buildpack ids were updated to Paketo or Tanzu Buildpack ids
- Projects resource api group changed from projects.pivotal.io to projects.vmware.com
No supported upgrade paths.