check-circle-line exclamation-circle-line close-line

VMware Tanzu Kubernetes Grid | 09 APR 2020 | Build 15961092

Check for additions and updates to these release notes.

What's in the Release Notes

The release notes cover the following topics:

About VMware Tanzu Kubernetes Grid

VMware Tanzu Kubernetes Grid provides Enterprise organizations with a consistent, upstream compatible, regional Kubernetes substrate across SDDC, Public Cloud, and Edge environments that is ready for end-user workloads and ecosystem integrations. TKG builds on trusted upstream and community projects and delivers an engineered and supported Kubernetes platform for end users and partners.

Key Features in Tanzu Kubernetes Grid 1.0

  • The Tanzu Kubernetes Grid installer interface, a graphical installer that walks you through the process of deploying management clusters to either vSphere or Amazon EC2.
  • The Tanzu Kubernetes Grid CLI, providing simple commands that allow you to deploy CNCF conformant Kubernetes clusters to either vSphere or Amazon EC2.
  • Binaries for Kubernetes and all of the components that you need in order to easily stand up an enterprise-class Kubernetes development environment. All binaries are tested and signed by VMware.
  • Extensions for your Tanzu Kubernetes Grid instance, that provide authentication and authorization, logging, networking, and ingress control. 
  • VMware support for your Tanzu Kubernetes Grid deployments.

User Documentation

The Tanzu Kubernetes Grid 1.0 documentation includes information about the following subjects:

Component Versions

The Tanzu Kubernetes Grid 1.0 release ships with the following software components:

  • kubernetes=v1.17.3+vmware.2:
  • coredns=v1.6.5+vmware.4
  • etcd=v3.4.3+vmware.4
  • cri_tools=v1.16.1+vmware.3
  • cni_plugins=v0.7.5+vmware.6
  • csi_livenessprobe=v1.1.0+vmware.7
  • csi_attacher=v1.1.1+vmware.7
  • csi_provisioner=v1.4.0+vmware.2
  • csi_registrar=v1.1.0+vmware.7
  • vsphere_csi_driver=v1.0.2+vmware.1
  • cloud_provider_vsphere=v1.1.0+vmware.2
  • cluster_api=v0.3.3+vmware.1
  • cluster_api_vsphere=v0.6.3+vmware.1
  • cluster_api_aws=v0.5.2+vmware.1
  • kube_rbac_proxy=v0.4.1+vmware.2
  • calico_all=v3.11.2+vmware.1 
  • tanzu_tkg_cli=v1.0.0+vmware.1
  • contour=v1.2.1+vmware.1
  • fluent_bit=v1.3.8+vmware.1
  • dex=v2.22.0+vmware.1
  • kubernetes_sigs_kind=v0.7.0-1.17.3+vmware.2
  • envoy=v1.13.1+vmware.1
  • containerd=v1.3.3+vmware.1
  • jetstack_cert_manager=v0.11.0+vmware.1
  • gangway=v3.2.0+vmware.1
  • crash_diagnostics=v0.2.2+vmware.1
  • haproxy_ova=v0.6.3+vmware.1
  • node_ova=v1.17.3+vmware.2
  • tkg_extension_manifest=v1.0.0+vmware.1

Amazon Machine Image IDs 

If you deploy Tanzu Kubernetes Grid to Amazon EC2, Tanzu Kubernetes Grid creates the management cluster and Tanzu Kubernetes cluster node VMs from standard Amazon Linux 2 Amazon Machine Images (AMI). A Tanzu Kubernetes Grid AMI is publicly available in every AWS region. The following table lists the Tanzu Kubernetes Grid AMI IDs for each AWS region for this release of Tanzu Kubernetes Grid.

Amazon Machine Images for Tanzu Kubernetes Grid 1.0.0
AWS Region AMI ID
ap-northeast-1 ami-07d5076afaf13aa77
ap-northeast-2 ami-0cb22de4c4da68542
ap-south-1 ami-0acc928b65d161ebd
ap-southeast-1 ami-089a436f0bace9335
ap-southeast-2 ami-083ec7e91a68e9c73
eu-central-1 ami-0d9f883266dee911e
eu-west-1 ami-0ec61dd68529b73e2
eu-west-2 ami-0e9216661312a1a35
eu-west-3 ami-05dfe276355eb8f12
sa-east-1 ami-0cfe19e780369d05f
us-east-1 ami-0cdd7837e1fdd81f8
us-east-2 ami-0f02df79b659875ec
us-west-1 ami-0ec28d83f96a31158
us-west-2 ami-074a82cfc610da035

Known Issues

The known issues are grouped as follows.

Installation Issues
  • Variables that include dollar symbols ($) are not interpreted correctly

    Due to an in issue in the version of clusterctl that Tanzu Kubernetes Grid uses, any variables that include $ that you pass to the Tanzu Kubernetes Grid CLI or installer interface are misinterpreted. This will be fixed in the next release of Tanzu Kubernetes Grid.

    Workaround: Do not include $ symbols in variables that you pass to Tanzu Kubernetes Grid. 

  • CSI provider fails if you specify domain accounts

    If you specify a domain user account in the format DOMAIN\username when you deploy Tanzu Kubernetes Grid management clusters, the container storage interface (CSI) provider fails with the error Err: 6:8: unquoted '\' must be followed by new line or double quote.

    Workaround: Always specify user accounts in the format username@fqdn.

  • Crash Recovery and Diagnostics Binary for Mac OS not included in download bundle

    The Crash Recovery and Diagnostics bundle that you download, crash-diagnostics-v0.2.2.tar, includes two package for Linux and Mac OS, crash-diagnostics-linux-v0.2.2.gz and crash-diagnostics-darwin-v0.2.2.gz. However, both packages contain the Linux binary.

    Use Crash Recovery and Diagnostics on Linux systems only.

vSphere Issues
  • Worker node clone operations can cause "the name already exists error" faults in vSphere

    Cloning node VMs from the template to worker nodes causes several vSphere Clone API calls to attempt to clone to same name, leading to an error being displayed in vSphere.

    These errors only appear in the vSphere client. The creation of the cluster succeeds.

    Workaround: None

  • tkg get cluster command does not return clusters running in vSphere with Kubernetes

    If you connect the Tanzu Kubernetes Grid CLI to the Supervisor Cluster in a vSphere with Kubernetes instance and run the tkg get cluster command, no clusters are returned. This is due to the Cluster API versions used by vSphere with Kubernetes and Tanzu Kubernetes Grid.

    Workaround: Use the kubectl vsphere CLI utility to get the list of clusters running in vSphere with Kubernetes.

Amazon EC2 Issues
  • Cluster creation on Amazon EC2 hangs if you specify a name that starts with "sg-"

    In Amazon EC2, sg is reserved for use by the Security Group. If attempt to deploy a cluster to Amazon EC2 with a name that starts with sg, the cluster creation hangs indefinitely and no error is returned.

    Workaround: Do not use sg as the first letters of cluster names when deploying clusters to Amazon EC2.