VMware Tanzu Kubernetes Grid | 21 MAY 2020 | Build 16242503 Check for additions and updates to these release notes. |
What's in the Release Notes
About VMware Tanzu Kubernetes Grid
- 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
- Output
tkg get management-cluster
to JSON or YAML files - Output
tkg get cluster
to JSON or YAML files
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. Thetkg
andkubectl
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 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
Supported AWS Regions
Timer Utility 5 V1 0 0 X Reader
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
![Timer utility 5 v1 0 0 x 24 Timer utility 5 v1 0 0 x 24](https://vvvv.org/sites/default/files/TimerTool_0.png)
- 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.
Component Versions
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
- Variables that include dollar symbols ($) are not interpreted correctlyDue 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 accountsIf you specify a domain user account in the format
DOMAINusername
when you deploy Tanzu Kubernetes Grid management clusters, the container storage interface(CSI) provider fails with the errorErr: 6:8: unquoted ' must be followed by new line or double quote
. - Crash Recovery and Diagnostics Binary for Mac OS not included in download bundleThe 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
andcrash-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 vSphereCloning 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 KubernetesIf 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
- Tanzu Kubernetes Grid UI does not display correctly on WindowsWhen 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 toapplication/x-css
.Workaround:- In Windows search, enter
regedit
to open the Registry Editor utility. - Expand
HKEY_CLASSES_ROOT
and select.css
. - Right-click Content Type and select Modify.
- Set the Value to
text/css
and click OK. - Run the
tkg init --ui
command again to relaunch the UI.
- In Windows search, enter
- Creating Kubernetes v1.17.3 clusters failsIf 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 errorvSphere 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 theVSPHERE_TEMPLATE
setting in your.tkg/config.yaml
file points tophoton-3-kube-v1.18.2+vmware.1
.Workaround: Change theVSPHERE_TEMPLATE
setting in your.tkg/config.yaml
file tov1.17.3+vmware.2
and run thetkg create cluster
command again.
- Cannot log back in to vSphere 7 Supervisor Cluster after connection expiresWhen you use
kubectl vsphere login
to log in to a vSphere 7 Supervisor Cluster, thekubeconfig
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 usekubectl vsphere login
to log in to the Supervisor Cluster again, get the newkubeconfig
, and attempt to runtkg add management-cluster cluster_name
to add the newkubeconfig
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:- Set an environment variable for
kubeconfig
:export KUBECONFIG=$HOME/.kube-tkg/config
- Run
kubectl vsphere login
.
This updates the Tanzu Kubernetes Grid management clusterkubeconfig
for vSphere 7 with Kubernetes without requiring you to update it by using thetkg add management-cluster
command. - Set an environment variable for
- Upgrade to 1.1 fails if the location of the management cluster has changedIf 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 charactersIf you set the
VSPHERE_SERVER
parameter in theconfig.yaml
file with a vCenter Server FQDN that includes upper-case letters, deployment of the management cluster fails with the errorCredentials not found
.Workaround: Use all lower-case letters when you specify a vCenter Server FQDN in theconfig.yaml
file.
- List of clusters shows incorrect Kubernetes version after unsuccessful upgrade attemptIf 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
Printable version |
|
Timer Utility 5 V1 0 0 X 4
|