How are buildpacks supported by Tanzu?

Products

• VMware Tanzu Application Service for VMs

Issue/Introduction

This article discusses how buildpacks and dependencies packaged with buildpacks are supported by VMware.

VMware provides buildpacks with VMware Tanzu Application Service for VMs (TAS) that can be used to runs your applications. Each buildpack may install and configure one or more servers, language, runtime and/or the framework to be used by your application.

At the time of writing this article, we provide the following officially supported buildpacks.

• NodeJS
• PHP
• Python
• R
• Ruby
• tc Server
• HWC
• Nginx
• Java
• Go
• Binary
• Staticfile
• .NET Core

This list is subject to change over time. 

Resolution

VMware provides the following support for all official buildpacks.

• VMware monitors dependencies bundled with buildpacks for updates and security fixes. When dependencies are updated, VMware will generate a new version of the buildpack that includes the new dependencies and patched dependencies. VMware will retain the two most recent maintenance releases of each supported minor version of a dependency with each buildpack. For example, if there is a new release of Ruby. VMware will update the Ruby buildpack and cut a new release that includes the new latest version of Ruby while, at the same time, dropping the oldest version that was previously bundled (i.e. N-3 is dropped).
• VMware will assist in troubleshooting issues that occur when the buildpack is being used. Primarily, this troubleshooting will focus on determining whether the problem is related to the buildpack or how the buildpack configured the application and dependencies and if the problem is with the dependencies installed by the buildpack or if it's with the application itself.
  • VMware will fix bugs related to the buildpack itself. This includes bugs which affect the operation of the buildpack, how it installs dependencies, and how it configures software for use by your application. It does not cover tools that the buildpack might execute to help prepare your application to run. For example, it will not cover bugs in a package management tool like Bundler, NPM, Nuget or Composer.
  • VMware will provide assistance with tools and dependencies that are installed by the native buildpack itself. 
  • If VMware Support determines that the issue is with the application being run by the buildpack, then this is not supported. This extends to custom configurations as well. For example, buildpacks like the Nginx buildpack and the PHP buildpack allow you to specify completely custom configurations for the server. VMware Support does not cover custom codes or configurations, please see our terms and conditions.

The following graphic visualizes what is covered and what is not covered by VMware Support for buildpacks.

Please also be aware of the following notes regarding VMware by Broadcom TANZU Buildpack Support.

• VMware only supports the most current release of an unmodified/non-forked buildpack. If you are encountering an issue with an older buildpack, Tanzu Support customer will be asked to upgrade to a current supported version, and retry.  
• VMware will never patch or update an existing buildpack. All buildpack fixes and dependency updates will be issued in the form of new buildpacks. Customers will need to upgrade to the latest buildpack to get fixes and updated dependencies.

Additional Information

There are a few exceptions to the policy described above.

• VMware will support the unmodified versions of OpenJDK bundled with the Java buildpack when used by applications running on TAS.
• VMware provides support for Apache Tomcat & tc Server, which are dependencies installed by the unmodified Java buildpack. These servers are supported when run on TAS or when run stand-alone.
• VMware will provide application level support for customers that have deployed Java applications utilizing the Spring Framework & Spring Boot (using unmodified buildpacks). The scope of this support is covered in another KB.