VMware Tanzu Build Service automates container creation, management, and governance at enterprise scale. Tanzu Build Service uses the open-source Cloud Native Buildpacks project to turn application source code into container images. It executes reproducible builds aligned with modern container standards and keeps images up to date. For more information about Tanzu Build Service, see the Tanzu Build Service Documentation.
On non-air-gapped clusters, dependencies are imported as a part of installation of a Tanzu Application Platform profile or the Tanzu Build Service component.
When creating the values file during installation, include the
descriptor_name key-value pairs, in addition to any other
buildservice key-value pairs, as in this example:
… kp_default_repository: REPOSITORY kp_default_repository_username: REGISTRY-USERNAME kp_default_repository_password: REGISTRY-PASSWORD tanzunet_username: TANZUNET-USERNAME tanzunet_password: TANZUNET-PASSWORD descriptor_name: DESCRIPTOR-NAME …
TANZUNET-PASSWORDare the email address and password that you use to log in to VMware Tanzu Network.
DESCRIPTOR-NAMEis the name of the descriptor to import automatically. For more information, see Descriptors. Available options are:
liteis the default if not set. It has a smaller footprint, which enables faster installations.
fullis optimized to speed up builds and includes dependencies for all supported workload types.
Tanzu Build Service descriptors are curated sets of dependencies, including stacks and buildpacks, that are continuously released on VMware Tanzu Network to resolve all workload Critical and High CVEs. Descriptors are imported into Tanzu Build Service to update the entire cluster.
There are two types of descriptor,
full. The different descriptors can apply to different use cases and workload types. You can configure which descriptor is imported after installation when installing Tanzu Application Platform or the Tanzu Build Service component.
For more information, see Descriptors.
You can configure Tanzu Build Service to update dependencies in the background as they are released. This enables workloads to keep up to date automatically.
When creating the values file during installation, include the key-value pair
enable_automatic_dependency_updates: true, in addition to any other
buildservice keys, as in this example:
... kp_default_repository: REPOSITORY kp_default_repository_username: REGISTRY-USERNAME kp_default_repository_password: REGISTRY-PASSWORD tanzunet_username: TANZUNET-USERNAME tanzunet_password: TANZUNET-PASSWORD descriptor_name: DESCRIPTOR-NAME enable_automatic_dependency_updates: true ...
Sometimes you might not want Tanzu Build Service to automatically update dependencies in the background.
In this case, you can manually manage and update your dependencies individually or automate the updating configuration yourself in a CI/CD context.
The Tanzu Build Service package in Tanzu Application Platform behaves identically to the standalone Tanzu Build Service product described in the Tanzu Build Service documentation.
For updating dependencies manually, see Updating Build Service Dependencies.