Skip to content

Latest commit

 

History

History
96 lines (64 loc) · 5.11 KB

File metadata and controls

96 lines (64 loc) · 5.11 KB

Release notes

{{#unless vars.hide_content}} This Handlebars condition is used to hide content. In release notes, this condition hides content that describes an unreleased patch for a released minor. {{/unless}}

This topic contains release notes for Tanzu Application Platform v1.4.

v1.4.0

Release Date: January 10, 2023

New features

This release includes the following changes, listed by component and area.

TAP

TAP is introducing a shared ingress issuer for secure ingress communication by default. CNRs, AppSSO, and TAP GUI are using this issuer to secure ingress. In upcoming releases all components will support it eventually.

Tanzu Application Platform GUI Plug-ins

Supply Chain Choreographer Plug-in

  • Events are now emitted when resources are being applied, or their output or health status changed.
  • Source Tester stage now includes a link to the Jenkins job when Jenkins is configured for use in the supply chain.
  • spec.source.git.url is added to the Overview section of the Source Provider stage in the supply chain.
  • Added support to include current and historical Kaniko build logs in the Stage Details section of the supply chain when Kaniko is used as the build service in the Image Provider stage.
  • Scanning stages now include a Show Unique CVEs filter so that the scan results show one CVE per ID as opposed to each CVE per package. This allows better alignment between the data in the Supply Chain Choreographer plug-in and the Security Analysis plug-in.
  • View Approvals is relocated to the Config Writer stage, instead of being a stage by itself.
  • Added an Impacted Workloads column to the Stage Details section of scanning stages, so that it is now easier to see how many workloads are impacted by the CVE that the scan detected.

Breaking changes

This release has the following breaking changes, listed by area and component.

Tanzu Developer Tools for Visual Studio Code

  • Tanzu Debug no longer port forwards the application port (8080).

Supply Chain Security Tools - Image Policy Webhook

The Image Policy Webhook component is removed in TAP 1.4 after being deprecated in favor of the Policy Controller

Supply Chain Security Tools - Policy Controller

Policy Controller no longer initializes TUF by default. TUF is required to support the keyless authorities in ClusterImagePolicy. To continue to use keyless authorities, provide the value policy.tuf_enabled: true by using the tap-values.yaml while upgrading. By default, the public Sigstore The Update Framework (TUF) server is used. To target an alternative Sigstore stack, specify policy.tuf_mirror and policy.tuf_root.

Security fixes

This release has the following security fixes, listed by area and component.

Supply Chain Security Tools - Grype

  • python has been updated to 3.7.5-22.ph3

Resolved issues

The following issues, listed by area and component, are resolved in this release.

API Auto Registration

  • Now periodically checks the original API specification from the defined location to find changes, and registers any changes into the API Descriptor, triggering also the reconciliation into the Tanzu Application Platform GUI catalog. This synchronization period or frequency is configurable through the new value sync_period. The default value is 5 minutes.
  • Base image updated to resolve CVE-2022-3786 and CVE-2022-3602.

Tanzu Application Platform GUI Plug-ins

  • Immediate entity provider backend Plug-in

    • The entity provider (used mainly by API Auto Registration) now allows a body size of 5Mb (increased from 100Kb) to accept larger API specs.
    • Respecting the restriction of Backstage for Entity Provider mutations, whenever an existing entity is intended for a mutation through this plugin, and its origin is a different entity provider, a 409 Conflict error is returned.

Supply Chain Choreographer Plug-In

  • The UI no longer shows the error Unable to retrieve details from Image Provider Stage when the Builder is not available or configured. It now correctly shows the same error as the CLI, Builder default is not ready.

Known issues

This release has the following known issues, listed by area and component.