TAS for Kubernetes Release Notes

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

v0.3.0

Release Date: July 30, 2020

Product Snapshot

Release Details
Version v0.3.0
Release date July 30, 2020

To download VMware Tanzu Application Service 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:

Element Details
cf-for-k8s Commit 9854f5b
Istio v1.4.5
kpack v0.0.9

Required Additional Components

TAS for Kubernetes requires the following components:

Element Details
BOSH CLI v6.3.1
cf CLI v6.51.0
kapp v0.29.0 or later
kbld v0.23.0 or later
ytt v0.28.0 or later

Supported Kubernetes Distributions

TAS for Kubernetes supports the following Kubernetes distributions:

Platform Version
Tanzu Kubernetes Grid v1.0, with metrics-server
VMware Enterprise PKS v1.6 or v1.7

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 with VMware Enterprise PKS.
  • Uses the k14s toolchain (ytt, kbld, and kapp) for installation. For more information, see the k14s 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.