VMware Telco Cloud PlatformTM – 5G Edition | 14 JAN 2021
NOTE: This Release Notes does not provide the terms applicable to your license. Consult the VMware Product Guide and VMware End User License Agreement for the license metrics and other license terms applicable to your use of VMware Telco Cloud Platform.
Check for additions and updates to these release notes.
What's in the Release NotesThe release notes cover the following topics:
- What's New
- Components of Telco Cloud Platform 5G Edition 2.0
- Support Resources
- Resolved Issues
- Known Issues
Carrier-Grade Virtual & Container Network Function Automation and Orchestration
VMware Telco Cloud Automation 1.8 includes the following new features and enhancements:
- VMware Tanzu Kubernetes Grid (TKG) CaaS clusters and node pools can now be upgraded by VMware Telco Cloud Automation.
- Role-Based Access Control (RBAC) for CaaS infrastructure automation
- Ability to install and configure Antrea as part of the CaaS lifecycle management.
- Support for Harbor 2.x as a Partner System.
For more information about these features, see the VMware Telco Cloud Automation 1.8 Release Notes.
Note: VMware Telco Cloud Automation allows automatic wiring of standard and SR-IOV accelerate workloads only.
Carrier-Grade Kubernetes Infrastructure
VMware Tanzu Standard for Telco introduces the following features and enhancements:
- New Kubernetes versions:
- Support for cluster monitoring with Prometheus (with Alert Manager) and Grafana.
- Ability to choose Antrea as the default CNI.
For more information about these features and enhancements, see the VMware Tanzu Kubernetes Grid 1.2 Release Notes.
Carrier-Grade Resilient Networking
VMware NSX-T Data Center 3.1 introduces various new features for virtualized networking and security for private, public, and multi-clouds.
- Cloud-scale Networking: Federation enhancements and Enhanced Multicast capabilities.
- Move to Next-Gen SDN: Simplified migration from NSX-V to NSX-T.
- Intrinsic Security: Distributed IPS and FQDN-based Enhancements.
- Lifecycle and monitoring: NSX-T support with vSphere Lifecycle Manager (vLCM), simplified installation, enhanced monitoring, search and filtering.
For more information about these features, see the VMware NSX-T Data Center 3.1 Release Notes.
Workload Compute Performance
VMware vSphere 7.0 Update 1 introduces the following new features and enhancements:
- Enhanced vSphere Lifecycle Manager hardware compatibility pre-checks for vSAN environments
- Increased number of vLCM concurrent operations on clusters
- vLCM support for coordinated updates between availability zones
- Virtual hardware version 18
- Increased resource maximums for virtual machines and performance enhancements
For information about these features and enhancements, see the VMware vSphere 7.0 Update 1 Release Notes.
- VMware ESXi 7.0 U1. See the VMware ESXi 7.0 Update 1 Release Notes.
- VMware vRealize Orchestrator Appliance 8.2. See the VMware vRealize Orchestrator 8.2 Release Notes.
- VMware NSX-T Data Center Advanced Edition 3.1. See the VMware NSX-T Data Center 3.1 Release Notes.
- VMware Telco Cloud Automation 1.8. See the VMware Telco Cloud Automation 1.8 Release Notes.
- VMware Tanzu Kubernetes Grid 1.2. See the VMware Tanzu Kubernetes Grid 1.2 Release Notes.
Mandatory Add-On Components
Note: Additional license is required.
- VMware vCenter Server 7.0 U1a. See the VMware vCenter Server 7.0 Update 1a Release Notes.
- VMware ESXi 7.0 U1a. See the VMware ESXi 7.0 Update 1a Release Notes.
For additional support resources, see the VMware Telco Cloud Platform documentation page.
- Node Pool VMs Exist in vSphere Even After Successful Deletion of Node Pool in Telco Cloud Automation
This issue in fixed in VMware Telco Cloud Automation 1.8.
- Scale-out Operation Failed During SR-IOV Customization on New Node
This issue is fixed in VMware Telco Cloud Automation 1.8.
- Association of Harbor Registry with Kubernetes Cluster Not Recorded Properly in Telco Cloud Automation
When you deploy CNFs on a Kubernetes cluster, the Harbor registry associated with the cluster does not appear for selection in the Telco Cloud Automation UI. In this issue, the Harbor registry is associated with the Kubernetes cluster properly but is not recorded in the Telco Cloud Automation database.
Workaround: Navigate to the Partner Systems UI, modify the Harbor registry, and add the VIM association.
- Users with Infrastructure LCM Privilege Are Not Able to Delete Kubernetes Clusters
Users with the Infrastructure LCM privilege are not able to delete Kubernetes clusters that are deployed through VMware Telco Cloud Automation.
Workaround: Add the Virtual Infrastructure Admin privilege to users.
- Virtual Infrastructure Admin Cannot Edit Workload Clusters Successfully
If an advanced filter is applied to the Kubernetes cluster instance name, VMware Tanzu Kubernetes Grid Admin cannot edit the Kubernetes cluster configuration successfully.
Workaround: To manage a Kubernetes Workload cluster as a VIM, the Admin must have at least Read-Only access to the corresponding Kubernetes Management cluster. With VIM Read-Only access, the Admin can create new permission with the Virtual Infrastructure Auditor role and the Management cluster as the VIM filter.
- Partner System Admin User Cannot Associate VIMs with an Existing Harbor
If a Partner System Admin user associates a VIM with an existing Harbor, the association fails with the registration successful message.
Workaround: System Admin User can associate VIMs with an existing Harbor.
- Partner System Admin Users Can View Other Registered Partner Systems
When configuring permissions for a Partner System Admin user, the associated Partner System is not available as an object type under advanced filter criteria. Hence, the user can view other registered Partner Systems also.
- Registration of Multiple Harbor Systems with a Single VIM is Not Supported
VMware Telco Cloud Automation does not support the registration of multiple Harbor systems with a single VIM.
- VMXNET Not Supported During CNF Instantiation
VMXNET usage is not supported during CNF instantiation.
Workaround: Use VMXNET during the cluster creation.
- TCA Virtual Infrastructure Main Dashboard Does Not Show the Resource Consumption for Virtual Infrastructure
The resource consumption for virtual infrastructure is not shown on the TCA virtual infrastructure main dashboard.