vCenter 7.0 Update 0a Released

VMware has released vCenter 7.0 Update 0a, and this also includes an update to vSphere with Kubernetes.

vCenter 7.0 Update 0a

This fixes a problem with a conflict between Lifecycle Manager, and vSAN File Services.

See the release notes here.

vSphere with Kubernetes

New Features

  • Tanzu Kubernetes Grid Service for vSphere: rolling upgrade and services upgrade
    • Customers can now perform rolling upgrades over their worker nodes and control plane nodes for the Tanzu Kubernetes Grid Service for vSphere, and upgrade the pvCSI, Calico, and authsvc services. This includes pre-checks and upgrade compatibility for this matrix of services.
    • Rolling upgrades can be used to vertically scale worker nodes, i.e. change the VM class of your worker nodes to a smaller or larger size.
  • Supervisor cluster: new versions of Kubernetes, upgrade supported
    • The Supervisor cluster now supports Kubernetes 1.17.4
    • The Supervisor cluster now supports upgrading from Kubernetes 1.16.x to 1.17.x

Resolved Issues

  • Naming conflict for deleted namespaces
    • We have resolved an issue where if a user deleted a vSphere namespace, and then created a new vSphere namespace with the same name, we had a naming collision that resulted in being unable to create Tanzu Kubernetes Grid workload clusters.
  • Improved distribution names
    • We have made it clearer what version of Kubernetes you are running by removing OVF versioning information to a separate column.

See the release notes here.

Please share this page if you find it usefull:

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.