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
- New Features in Tanzu Kubernetes Grid 1.1
- Behavior Changes Between Tanzu Kubernetes Grid 1.0 and 1.1
- Supported Kubernetes Versions in Tanzu Kubernetes Grid 1.1.0
- Supported Upgrade Paths
- Supported AWS Regions
- User Documentation
- Component Versions
- Resolved Issues
- Known Issues
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
- Support for upgrading Tanzu Kubernetes Grid 1.0 to 1.1 and Kubernetes 1.18.2
- Tanzu Kubernetes Grid CLI for Windows
- Ability to specify different sizes of control plane nodes and worker nodes for management clusters on vSphere and Amazon EC2
- Ability to select clusters and individual hosts when deploying management clusters to vSphere
- Ability to select an existing VPC when deploying management clusters to Amazon EC2
- Improved pre-deployment checks when deploying management clusters on vSphere and Amazon EC2
- MachineHealthCheck is deployed by default on clusters
tkg get management-clusterto JSON or YAML files
tkg get clusterto JSON or YAML files
Behavior Changes Between Tanzu Kubernetes Grid 1.0 and 1.1
- Improvements to the output of
tkg get clustercommand
- Delete management clusters by name rather than by context
- Tanzu Kubernetes Grid no longer automatically sets the
kubectlcontext to a Tanzu Kubernetes cluster when you create it. The
kubectlcontexts 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?|
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:
The Tanzu Kubernetes Grid 1.1 documentation includes information about the following subjects:
- Tanzu Kubernetes Grid Concepts introduces the key components of Tanzu Kubernetes Grid and describes how you use them and what they do.
- Installing Tanzu Kubernetes Grid describes the prerequisites for installing Tanzu Kubernetes Grid on vSphere and on Amazon EC2, and how to deploy the Tanzu Kubernetes Grid management cluster to both vSphere and Amazon EC2.
- Deploying Tanzu Kubernetes Clusters and Managing their Lifecycle describes how to use the Tanzu Kubernetes Grid CLI to deploy Tanzu Kubernetes clusters from your management cluster, and how to manage the lifecycle of those clusters.
- Configuring and Managing the Tanzu Kubernetes Grid Instance describes how to set up local shared services for your Tanzu Kubernetes clusters, such as authentication and authorization, logging, networking, and ingress control.
- Upgrading Tanzu Kubernetes Grid describes how to upgrade from version 1.0.0 to version 1.1.0.
- Troubleshooting Tips for Tanzu Kubernetes Grid includes tips to help you to troubleshoot common problems that you might encounter when installing Tanzu Kubernetes Grid and deploying Tanzu Kubernetes clusters.
- Tanzu Kubernetes Grid CLI Reference lists all of the commands and options of the Tanzu Kubernetes Grid CLI, and provides links to the section in which they are documented.
The Tanzu Kubernetes Grid 1.1 release ships with the following software components:
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
clusterctlthat 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\usernamewhen 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-darwin-v0.2.2.gz. However, both packages contain the Linux binary.
- 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 clustercommand, no clusters are returned. This is due to the Cluster API versions used by vSphere with Kubernetes and Tanzu Kubernetes Grid.
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 --uicommand 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
- In Windows search, enter
regeditto open the Registry Editor utility.
- Right-click Content Type and select Modify.
- Set the Value to
text/cssand click OK.
- Run the
tkg init --uicommand again to relaunch the UI.
- In Windows search, enter
- 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 clustercommand with
--kubernetes-version v1.17.3+vmware.2specified, 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_TEMPLATEsetting in your
.tkg/config.yamlfile points to
Workaround: Change the
VSPHERE_TEMPLATEsetting in your
v1.17.3+vmware.2and run the
tkg create clustercommand again.
- Cannot log back in to vSphere 7 Supervisor Cluster after connection expires
When you use
kubectl vsphere loginto log in to a vSphere 7 Supervisor Cluster, the
kubeconfigfile 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 loginto log in to the Supervisor Cluster again, get the new
kubeconfig, and attempt to run
tkg add management-cluster cluster_nameto add the new
.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
- Set an environment variable for
kubectl vsphere login.
This updates the Tanzu Kubernetes Grid management cluster
kubeconfigfor vSphere 7 with Kubernetes without requiring you to update it by using the
tkg add management-clustercommand.
- Set an environment variable for
- 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_SERVERparameter in the
config.yamlfile 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
- 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 clusterto see the list of deployed clusters and their versions, the cluster for which the upgrade failed shows the upgraded version of Kubernetes.