The EoS or EoL date of TPCF buidlapcks
Article ID: 428310
Updated On:
Products
Issue/Introduction
The KB article How are buildpacks supported by Tanzu describes general support policy of the Tanzu Platform for Cloud Foundry (TPCF) buldpacks. However, the user might want to know the End of Service (EoS) or End of Life (EoL) date of TPCF buildpacks as they are not shown on the product lifecycle portal. For example, no End of Service and End of Life dates for Java buildpack on the product lifecycle portal.
** Tanzu Platform for Cloud Foundry (TPCF) is formerly known as Tanzu Application Service (TAS)
Resolution
Basically there is no EoS or EoL date for TPCF buildpacks. Customer can always raise a support ticket for issues with a TPCF buildpack regardless of its version as long as they are on a supported version of TPCF.
However, as stated in the KB article How are buildpacks supported by Tanzu:
- If you are encountering an issue with an older buildpack, you need to upgrade to the latest version and retry
- No patch or update for 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.
Some standalone binaries or components included in a buildpack might have its own EoS date. For example, the EoS date of JRE/JDK component within Java buildpack can be found at Support Lifecycle section of VMware Tanzu Distribution of OpenJDK.
Additional Information
Feedback
