This topic provides information to help troubleshoot Tanzu Build Service when used with Tanzu Application Platform.
After upgrading to Tanzu Application Platform v1.2, you see failing builds.
After the upgrade, Tanzu Build Service image resources automatically run a build that fails due to a missing dependency.
This error does not persist and any subsequent builds will resolve this error.
You can safely wait for the next build of the workloads, which is triggered by new source code changes.
If you do not want to wait for subsequent builds to run automatically, you can use the open source kp CLI to re-run failing builds:
List the image resources in the developer namespace by running:
kp image list -n DEVELOPER-NAMESPACE
DEVELOPER-NAMESPACE is the namespace where workloads are created.
Manually trigger the image resources to re-run builds for each failing image by running:
kp image trigger IMAGE-NAME -n DEVELOPER-NAMESPACE
IMAGE-NAMEis the name of the failing image.
DEVELOPER-NAMESPACEis the namespace where workloads are created.
After installing Tanzu Application Platform on or upgrading an existing Amazon Elastic Kubernetes Service (EKS) cluster to Kubernetes v1.23, build pods show:
'running PreBind plugin "VolumeBinding": binding volumes: timed out waiting for the condition'
This is due to the CSIMigrationAWS in this Kubernetes version, which requires users to install the Amazon EBS CSI driver to use AWS Elastic Block Store (EBS) volumes. For more information about EKS support for Kubernetes v1.23, see the Amazon blog post.
Tanzu Application Platform uses the default storage class which uses EBS volumes by default on EKS.
Follow the AWS documentation to install the Amazon EBS CSI driver before installing Tanzu Application Platform, or before upgrading to Kubernetes v1.23.