VMware Tanzu Kubernetes Grid | 25 JUN 2020 | Build 16444468

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

Behavior Changes Between Tanzu Kubernetes Grid 1.1.0 and 1.1.2

  • The VSPHERE_TEMPLATE setting is detected automatically when using the CLI to deploy management clusters to vSphere.
  • The .tkg/config.yaml file is populated at the Review Configuration stage when using the installer interface to deploy management clusters, rather than when you start the deployment, on both vSphere and Amazon EC2.

Supported Kubernetes Versions in Tanzu Kubernetes Grid 1.1.2

Tanzu Kubernetes Grid 1.1.2 adds support for Kubernetes 1.18.3 and 1.17.6. This version also supports the versions of Kubernetes from previous versions of Tanzu Kubernetes Grid.

Tanzu Kubernetes Grid Version Provided Kubernetes Versions Supported in v1.1.2?
1.1.2 1.18.3
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 and v1.1.0 to version 1.1.2.

Supported AWS Regions

You can use Tanzu Kubernetes Grid 1.1.2 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-gov-east-1
  • us-gov-west-1
  • us-west-2

User Documentation

The Tanzu Kubernetes Grid 1.1 documentation covers both the 1.1.0 and 1.1.2 releases. It includes information about the following subjects:

Component Versions

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

  • calico_all: v3.11.2+vmware.1
  • cloud-provider-azure: v0.5.1+vmware.1
  • cloud_provider_vsphere: v1.1.0+vmware.2
  • cluster-api-provider-azure: v0.4.4+vmware.1
  • cluster_api: v0.3.6+vmware.1
  • cluster_api_aws: v0.5.4+vmware.1
  • cluster_api_vsphere: v0.6.5+vmware.1
  • cni_plugins: v0.8.5+vmware.1
  • containerd: v1.3.4+vmware.1
  • contour: v1.2.1+vmware.1
  • coredns: v1.6.7+vmware.1
  • crash-diagnostics: v0.2.2+vmware.3
  • cri_tools: v1.17.0+vmware.1
  • csi_attacher: v2.0.0+vmware.1
  • csi_livenessprobe: v1.1.0+vmware.7
  • csi_node_driver_registrar: v1.2.0+vmware.1
  • 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.3+vmware.1
  • kubernetes-sigs_kind: v0.7.0-1.18.3+vmware.1
  • node_ova: v1.18.3+vmware.1,1.17.6+vmware.1
  • tanzu_tkg-cli: v1.1.2+vmware.1
  • tkg_extension_manifest: v1.1.0+vmware.1
  • vsphere_csi_driver: v2.0.0+vmware.1

Resolved Issues

The resolved issues are grouped as follows.

Installation Issues
  • 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


Known Issues

The known issues are grouped as follows.

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 with context already exists


    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.

  • Cluster API Provider vSphere stops unexpectedly when the VirtualMachine configuration is unavailable

    If Cluster API Provider vSphere cannot read the UUID of a virtual machine it stops unexpectedly because the error is not detected. For more information, see https://github.com/kubernetes-sigs/cluster-api-provider-vsphere/issues/944

    Workaround: The fix has been made in Cluster API Provider vSphere and will be picked up in a Tanzu Kubernetes Grid patch release.

Deployment Issues
  • May 2021 Linux security patch causes kind clusters to fail during management cluster creation

    If you run Tanzu Kubernetes Grid CLI commands on a machine with a recent Linux kernel, for example Linux 5.11 and 5.12 with Fedora, kind clusters do not operate. This happens because kube-proxy attempts to change nf_conntrack_max sysctl, which was made read-only in the May 2021 Linux security patch, and kube-proxy enters a CrashLoopBackoff state. The security patch is currently being backported to all LTS kernels from 4.9 onwards, so as  operating system updates are shipped, including for Docker Machine on Mac OS and Windows Subsystem for Linux, kind clusters will fail, resulting in management cluster deployment failure.

    Workaround: Update your version of kind to at least v.1.11.0, and run tkg init with the --use-existing-bootstrap-cluster option. For more information, see Use an Existing Bootstrap Cluster to Deploy Management Clusters.

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

check-circle-line exclamation-circle-line close-line
Scroll to top icon