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

VMware Tanzu Kubernetes Grid | 21 MAY 2020 | Build 16242503

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 include:

  • 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.

New Features in Tanzu Kubernetes Grid 1.1

Behavior Changes Between Tanzu Kubernetes Grid 1.0 and 1.1

  • Improvements to the output of tkg get cluster command
  • Delete management clusters by name rather than by context
  • Tanzu Kubernetes Grid no longer automatically sets the kubectl context to a Tanzu Kubernetes cluster when you create it. The tkg and kubectl contexts are still automatically set to a management cluster when you create it.

Supported Kubernetes Versions in Tanzu Kubernetes Grid 1.1.0

Tanzu Kubernetes Grid 1.1.0 adds support for Kubernetes 1.18.2. This version also supports the versions of Kubernetes from the previous version of Tanzu Kubernetes Grid.

Tanzu Kubernetes Grid Version Provided Kubernetes Versions Supported in v1.1.0?
1.1.0 1.18.2 YES
1.0.0 1.17.3 YES

Supported Upgrade Paths

You can upgrade Tanzu Kubernetes Grid v1.0.0 to v1.1.0.

Supported AWS Regions

You can use Tanzu Kubernetes Grid 1.1.0 to deploy clusters to the following AWS regions:

  • ap-northeast-1
  • ap-northeast-2
  • ap-south-1
  • ap-southeast-1
  • ap-southeast-2
  • eu-central-1
  • eu-west-1
  • eu-west-2
  • eu-west-3
  • sa-east-1
  • us-east-1
  • us-east-2
  • us-west-2

User Documentation

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

Component Versions

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

  • calico_all: v3.11.2+vmware.1
  • cloud_provider_vsphere: v1.1.0+vmware.2
  • cluster_api: v0.3.5+vmware.1
  • cluster_api_aws: v0.5.3+vmware.1
  • cluster_api_vsphere: v0.6.4+vmware.1
  • cni_plugins: v0.8.5+vmware.1
  • containerd: v1.3.4+vmware.
  • contour: v1.2.1+vmware.1
  • coredns: v1.6.7+vmware.1
  • crash-diagnostics: v0.2.2+vmware.2
  • cri_tools: v1.17.0+vmware.1
  • csi_attacher: v1.1.1+vmware.7
  • csi_livenessprobe: v1.1.0+vmware.7
  • csi_node_driver_registrar: v1.1.0+vmware.7
  • csi_provisioner: v1.4.0+vmware.2
  • dex: v2.22.0+vmware.1
  • envoy: v1.13.1+vmware.1
  • etcd: v3.4.3+vmware.5
  • fluent-bit: v1.3.8+vmware.1
  • gangway: v3.2.0+vmware.1
  • haproxy_ova: v1.2.4+vmware.1
  • jetstack_cert-manager: v0.11.0+vmware.1
  • kube_rbac_proxy: v0.4.1+vmware.2
  • kubernetes: v1.18.2+vmware.1
  • kubernetes-sigs_kind: v0.7.0-1.18.2+vmware.1
  • node_ova: v1.18.2+vmware.1
  • tanzu_tkg-cli: v1.1.0+vmware.1
  • tkg_extension_manifest: v1.1.0+vmware.1
  • vsphere_csi_driver: v1.0.2+vmware.1

Resolved Issues

The resolved 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.

     

  • 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.

     

  • 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.

     

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.

  • 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.

     

Known Issues

The known issues are grouped as follows.

Installation Issues
  • Tanzu Kubernetes Grid UI does not display correctly on Windows

    When you run the tkg init --ui command on a Windows system, the UI opens in your default browser, but the graphics and styling are not applied. This happens because a Windows registry is set to application/x-css.

    Workaround

    1. In Windows search, enter regedit to open the Registry Editor utility. 
    2. Expand HKEY_CLASSES_ROOT and select .css.
    3. Right-click Content Type and select Modify.
    4. Set the Value to text/css and click OK.
    5. Run the tkg init --ui command again to relaunch the UI.
  • Creating Kubernetes v1.17.3 clusters fails

    If you attempt to create a Tanzu Kubernetes cluster that runs Kubernetes v1.17.3 by running the tkg create cluster command with --kubernetes-version v1.17.3+vmware.2 specified, the creation fails with the error vSphere template kubernetes version validation failed: Kubernetes version (v1.17.3+vmware.2) does not match that of the VM template (v1.18.2+vmware.1).

    This happens because the VSPHERE_TEMPLATE setting in your .tkg/config.yaml file points to photon-3-kube-v1.18.2+vmware.1

    Workaround: Change the VSPHERE_TEMPLATE setting in your .tkg/config.yaml file to v1.17.3+vmware.2 and run the tkg create cluster command again.

vSphere Issues
  • Cannot log back in to vSphere 7 Supervisor Cluster after connection expires

    When you use kubectl vsphere login to log in to a vSphere 7 Supervisor Cluster, the kubeconfig file that is generated expires after 10 hours. If you attempt to run Tanzu Kubernetes Grid CLI commands against the Supervisor Cluster after 10 hours have passed, you are no longer authorized to do so. If you use kubectl vsphere login to log in to the Supervisor Cluster again, get the new kubeconfig, and attempt to run  tkg add management-cluster cluster_name to add the new kubeconfig to .tkg/config, it throws an error:
    Error: : cannot save management cluster context to kubeconfig: management cluster 192.168.123.1 with context 192.168.123.1 already exists

    Workaround:

    1. Set an environment variable for kubeconfig: export KUBECONFIG=$HOME/.kube-tkg/config
    2. Run kubectl vsphere login.

    This updates the Tanzu Kubernetes Grid management cluster kubeconfig for vSphere 7 with Kubernetes without requiring you to update it by using the tkg add management-cluster command.

  • Upgrade to 1.1 fails if the location of the management cluster has changed

    If the location of the management cluster changed after initial deployment, for example because the cluster was renamed, upgrading the management cluster to version 1.1 fails with an error similar to the following:

    "error"="failed to reconcile VM: unable to get resource pool for management-cluster"

    Workaround: Do not change the name of the cluster on which you deploy management clusters.

  • Management cluster deployment fails if the vCenter Server FQDN includes uppercase characters

    If you set the VSPHERE_SERVER parameter in the config.yaml file with a vCenter Server FQDN that includes upper-case letters, deployment of the management cluster fails with the error Credentials not found.

    Workaround: Use all lower-case letters when you specify a vCenter Server FQDN in the config.yaml file.

Upgrade Issues
  • List of clusters shows incorrect Kubernetes version after unsuccessful upgrade attempt

    If you attempt to upgrade a Tanzu Kubernetes cluster and the upgrade fails, and if you subsequently run tkg get cluster to see the list of deployed clusters and their versions, the cluster for which the upgrade failed shows the upgraded version of Kubernetes.

    Workaround: None