Tanzu Application Service for Kubernetes Release Notes

This topic contains release notes for Tanzu Application Service for Kubernetes (TAS for Kubernetes).

v0.7.0

Release Date: January 21, 2020

Product Snapshot

To download VMware TAS for Kubernetes v0.7.0, see VMware Tanzu Application Service for Kubernetes on the VMware Tanzu Network.

Supported Kubernetes Distributions

TAS for Kubernetes is compatible with Kubernetes v1.16 and later, and is tested with the following Kubernetes distributions:

Installed With TAS for Kubernetes v0.7.0

TAS for Kubernetes uses the following components:

Required Additional Components

TAS for Kubernetes requires the following components:

Supported Environments

TAS for Kubernetes can be deployed and managed from the following desktop OS environments:

• 64-bit Mac OS
• 64-bit Linux OS

Features

New features and changes in this release:

• Enables TAS for Kubernetes CF API v2 staging endpoints.
• Security enhancements.

Breaking Changes

This release has not been tested against Tanzu Kubernetes Grid Integrated Edition.

Known Issues

This release has the following issues:

• Apps Manager does not support inviting members.
• Apps Manager does not support creating container networking policies for apps.

• On TKGm v1.2.0 and v1.2.1, the kapp utility may fail to delete CF due to the version of Antrea used in those environments.
  
  To work around this issue, specify a filter to exclude Antrea resources during deletion:

  kapp delete -a cf --filter '{"not":{"resource":{"kinds":["AntreaControllerInfo"]}}}'
  

• Staging applications fail during cf push if you exceed the maximum image label size when using containerd v1.4.0 and 1.4.1. Containerd version 1.4.1 is used by TKGm 1.2.1. To reduce the chances of exceeding the maximum image’s label size, reduce the number of buildpacks used by the cf-default-builder.

v0.6

Release Date: December 4, 2020

Product Snapshot

To download VMware TAS for Kubernetes v0.6, see VMware Tanzu Application Service for Kubernetes on the VMware Tanzu Network.

Supported Kubernetes Distributions

TAS for Kubernetes is compatible with Kubernetes v1.16 and later, and is tested with the following Kubernetes distributions:

Installed With TAS for Kubernetes v0.6

TAS for Kubernetes uses the following components:

Required Additional Components

TAS for Kubernetes requires the following components:

Supported Environments

TAS for Kubernetes can be deployed and managed from the following desktop OS environments:

• 64-bit Mac OS
• 64-bit Linux OS

Features

New features and changes in this release:

• TAS for Kubernetes incorporates Apps Manager
• TAS for Kubernetes incorporates Usage Service
• TAS for Kubernetes incorporates Tanzu Buildpacks (with support for airgapped app staging) for Java, NodeJS, PHP, .NET core, and Golang
• Security enhancements

Breaking Changes

This release has the following breaking changes:

• App registry configuration files used with TAS for Kubernetes v0.3.0 and earlier are not compatible with TAS for Kubernetes v0.6.0 and later. For information about the current app registry configuration file format, see Configure the App Image Registry and Use a Different Image Registry in Configuring Your App Image Registry.
  
• Deployment configuration files used with TAS for Kubernetes v0.3.0 and earlier are not compatible with TAS for Kubernetes v0.6.0 and later. For information on how to re-generate your deployment configuration files, see Generate Configuration Values in Installing TAS for Kubernetes.
  
• Endpoints related to staging apps in the CF v2 API are disabled. Clients should use equivalent endpoints in the v3 API instead.

Known Issues

This release has the following issues:

• Apps Manager does not support inviting members.
• Apps Manager does not support creating container networking policies for apps.
• Pushing apps or retrieving app logs with cf logs requires cf CLI v7.0.1 or later

v0.3.0

Release Date: July 30, 2020

Product Snapshot

To download VMware TAS for Kubernetes v0.3.0, see VMware Tanzu Application Service for Kubernetes on the VMware Tanzu Network.

Installed With 0.3.0

TAS for Kubernetes uses the following components:

Required Additional Components

TAS for Kubernetes requires the following components:

Supported Kubernetes Distributions

TAS for Kubernetes supports the following Kubernetes distributions:

Supported Environments

TAS for Kubernetes can be deployed and managed from the following desktop OS environments:

• 64-bit Mac OS
• 64-bit Linux OS

Features

New features and changes in this release:

• Platform operators can copy system-component images into another registry and deploy TAS for Kubernetes to use those relocated images.
• Platform operators can configure their own certificates on the TAS for Kubernetes ingress gateway for TLS termination.
• TAS for Kubernetes incorporates Paketo cloud-native buildpacks for Java, NodeJS, Go, .NET Core, PHP, HTTPD, and nginx.
• Istio sidecar proxies prevent all communication between apps on the Kubernetes Pod network.
• Bump Istio to version 1.4.5
• Bump kpack to version 0.0.9

Known Issues

This release has the following issues:

• Retrieving app and buildpack-staging logs with cf logs requires cf CLI v6.50.0 or later.
• App instance logs also include unfiltered logs from the Istio sidecar proxy process and can be noisy as a result.
• The cf buildpacks command shows an empty list of buildpacks.
• Does not support cf CLI buildpack-administration commands.
• App developers cannot select a buildpack for their buildpack-based apps.
• The TAS for Kubernetes ingress gateway service may interfere with traffic for other Kubernetes Services in the cluster.
• TAS for Kubernetes cannot use the AWS Elastic Container Registry as its app image registry.
• Does not support upgrading an existing TAS for Kubernetes installation to a new version.
• Does not support re-deploying TAS for Kubernetes with different credentials.

v0.2.0

Release Date: May 29, 2020

Features

New features and changes in this release:

• The cf app command now displays CPU and memory usage metrics for app instances.
• Component metrics for Cloud Controller are now available for Prometheus to scrape via conventional prometheus.io annotations.
• Load-balancer options are now configured via the enable_load_balancer template parameter instead of via moving template overlay files.
• Ingress routing without a Kubernetes-provisioned load balancer no longer creates the istio-ingressgateway Kubernetes service.

Resolved Issues

This release has the following fixes:

• Apps can now receive ingress traffic through both HTTP and HTTPS.
• Buildpack-staging logs are now streamed during cf push.
• Running cf restage now restages the app successfully.
• Running buildpack-based apps no longer requires the diego_docker feature flag to be set.

Known Issues

This release has the following issues:

• Retrieving app and buildpack-staging logs with cf logs requires cf CLI v6.50.0 or later.
• App instance logs also include unfiltered logs from the Istio sidecar proxy process and can be noisy as a result.
• The cf buildpacks command shows an empty list of buildpacks.
• Does not support cf CLI buildpack-administration commands.
• App developers cannot select a buildpack for their buildpack-based apps.
• The TAS for Kubernetes ingress gateway service may interfere with traffic for other Kubernetes Services in the cluster.
• TAS for Kubernetes cannot use the AWS Elastic Container Registry as its app image registry.
• Does not support upgrading an existing TAS for Kubernetes installation to a new version.
• Does not support re-deploying TAS for Kubernetes with different credentials.

v0.1.0

Release Date: April 14, 2020

Features

Key features in this release:

• Supports building and running apps from source files through cf push using system-provided cloud-native buildpacks for Java, Go, NodeJS, and .NET Core.
• Supports running apps packaged as Docker images.
• Supports routing HTTP traffic to apps.
• Supports retrieving logs from app-instance processes.
• Supports retrieving logs from cloud-native buildpack builds.
• Supports installation to Kubernetes clusters provisioned by Tanzu Kubernetes Grid Integrated Edition.
• Uses the Carvel toolchain (ytt, kbld, and kapp) for installation. For more information, see the Carvel website.
• Supports integration with VMware Harbor Registry, Google Container Registry, and DockerHub for storing app images.

Known Issues

This release has the following issues:

• Apps can receive ingress traffic only through HTTP and not HTTPS.
• Retrieving app and buildpack-staging logs with cf logs requires cf CLI v6.50.0 or later.
• Buildpack-staging logs are not streamed during cf push.
• App instance logs also include unfiltered logs from the Istio sidecar proxy process and can be noisy as a result.
• Running cf restage fails to re-stage the app.
• The cf buildpacks command shows an empty list of buildpacks.
• Does not support cf CLI buildpack-administration commands.
• App developers cannot select a buildpack for their buildpack-based apps.
• Running buildpack-based apps requires the diego_docker feature flag to be set.
• The TAS for Kubernetes ingress gateway service may interfere with traffic for other Kubernetes Services in the cluster.
• TAS for Kubernetes cannot use the AWS Elastic Container Registry as its app image registry.
• Does not support upgrading an existing TAS installation to a new version.
• Does not support re-deploying TAS with different credentials.