Uploaded February 2026 | Updated November 2026, 6 hours ago
The video provides a walkthrough demonstration of app onboarding capabilities on the Tanzu platform. Presented by Jame Gonzalez Aguilar, this is the second part of a two-part series. The first part reviewed app assessment features, which assessed and identified the application suitability for onboarding.
This demonstration focuses on the next steps, starting with the 'cf repo onboard application' command. This command creates all the necessary onboarding configurations and automatically applies a remediation recipe to fix the "log into files" technical challenge by directing logs to standard output. Once the application is ready, it is pushed to the platform using an autogenerated deployment manifest and the Java buildpack. A re-assessment confirms that the modernization challenge has been removed. The process then continues by publishing the Software Bill of Materials (SBOM) to review compliance and vulnerability issues. An incremental upgrade plan is generated, and a one step upgrade of the application from Java 11 to Java 17 is completed. Finally, the demo concludes by seeking and applying advice for optimization, specifically adding Spring Governance Starter to enforce security defaults and ensure adherence to standards like NIST/FIPS.
The video provides a walkthrough demonstration of app onboarding capabilities on the Tanzu platform. Presented by Jame Gonzalez Aguilar, this is the second part of a two-part series. The first part reviewed app assessment features, which assessed and identified the application suitability for onboarding.
This demonstration focuses on the next steps, starting with the 'cf repo onboard application' command. This command creates all the necessary onboarding configurations and automatically applies a remediation recipe to fix the "log into files" technical challenge by directing logs to standard output. Once the application is ready, it is pushed to the platform using an autogenerated deployment manifest and the Java buildpack. A re-assessment confirms that the modernization challenge has been removed. The process then continues by publishing the Software Bill of Materials (SBOM) to review compliance and vulnerability issues. An incremental upgrade plan is generated, and a one step upgrade of the application from Java 11 to Java 17 is completed. Finally, the demo concludes by seeking and applying advice for optimization, specifically adding Spring Governance Starter to enforce security defaults and ensure adherence to standards like NIST/FIPS.










