This topic gives you an overview of Tanzu Build Service (commonly known as TBS).
Overview
Tanzu Build Service uses the open-source Cloud Native Buildpacks project to turn application source code into container images. Build Service executes reproducible builds that align with modern container standards and keeps image resources up to date. It does so by leveraging Kubernetes infrastructure with kpack, a Cloud Native Buildpacks Platform, to orchestrate the image lifecycle. The kpack CLI tool, kp can aid in managing kpack resources.
Build Service helps you develop and automate containerized software workflows securely and at scale.
Build Service Concepts
Build Service reduces operational overhead and improves security by automating the building of application images. It relies on Image, Builder, ClusterStore, and ClusterStack to achieve these results.
Image Resource
An Image resource defines the source of the application, build time environment and registry destination. This source code could reside in git, a blobstore, or as code on a workstation.
For more information see the Managing Images and Builds page.
Builder
A Builder references the Stack and Buildpacks used in the process of building source code. They provide the Buildpacks that run against the application and the operating system (OS) images upon which the application is built and run.
For more information, see the Managing Builders page.
Buildpacks
A Buildpack or ClusterBuildpack represents a Cloud Native Buildpack available for use in Builders.
For more information, see the Managing Buildpacks page.
ClusterStore
A ClusterStore serves as a repository for Cloud Native Buildpacks available for use in Builders. You can populate a store with Buildpacks you create and package.
For more information, see the Managing ClusterStores page.
ClusterStack
A ClusterStack defines a pair of build and run OS images. Critical security vulnerabilities are addressed by building apps on the most up-to-date stack. The stacks used by Build Service to build applications are referenced in the Builders.
For more information, see the Managing ClusterStacks page.
Build Service components
Tanzu Build Service ships with the following components:
Build Service Dependencies
Buildpacks
Tanzu Build Service utilize Tanzu Buildpacks.
Stacks
Stack Documentation is available on the Tanzu Buildpacks documentation.
The following Stacks and their updates can be found on the Tanzu Build Service Dependencies page.
| Name | ID |
|---|---|
| tiny | io.paketo.stacks.tiny |
| base | io.buildpacks.stacks.bionic |
| full | io.buildpacks.stacks.bionic |
| tiny-jammy | io.paketo.stacks.jammy.tiny |
| base-jammy | io.buildpacks.stacks.jammy |
| full-jammy | io.buildpacks.stacks.jammy |
| static-jammy | io.buildpacks.stacks.jammy.static |
| standard-ubi-8 | io.buildpacks.stacks.ubi8.standard |
Dependencies
Tanzu Build Service dependencies are curated sets of stacks, buildpacks, and builders that are continuously released to resolve all workload Critical and High CVEs. You can configure dependencies to automatically update. For more information, see Updating Dependencies.
There are two types of dependencies available for Tanzu Build Service, lite and full. They can apply to different use cases and workload types. You can configure which dependencies to use when installing Tanzu Build Service.
For more information, see Dependencies.
Updating Build Service Dependencies
Build Service allows the user to update Buildpacks and Stacks via the kp CLI. You can learn more about updating Build Service Dependencies here.
Troubleshooting
For troubleshooting failed builds, check the FAQ section of our docs.
If you are unable to resolve your problem, please contact Tanzu VMware Support.
Notice of telemetry collection for Tanzu Build Service
Tanzu Build Service participates in the VMware Customer Experience Improvement Program (CEIP). As part of CEIP, VMware collects technical information about your organization’s use of VMware products and services in association with your organization’s VMware license keys. For information about CEIP, see the Trust & Assurance Center. You may join or leave CEIP at any time. The CEIP Standard Participation Level provides VMware with information to improve its products and services, identify and fix problems, and advise you on how to best deploy and use VMware products. For example, this information can enable a proactive product deployment discussion with your VMware account team or VMware support team to help resolve your issues. This information cannot directly identify any individual.
You must acknowledge that you have read the VMware CEIP policy before you can proceed with the installation. For more information, see Installing Tanzu Build Service. To opt out of telemetry participation after installation, see Opting out of telemetry collection.
