• The Cisco Container Platform Installer OVA

• The latest two versions of the tenant OVA

• A vCenter cluster with High Availability (HA) and Distributed Resource Scheduler (DRS) enabled

• A DHCP server that provides IP addresses to the Cisco Container Platform VMs

• A vCenter datastore that is mounted on all the ESX hosts in the cluster

• Cisco Container Platform control plane VMs needs to have network access to vCenter appliance API

• Cisco Container Platform 1.3.0 and later requires hypervisor hosts to be running CPUs with an Ivy Bridge or newer microarchitecture.

• Fixed IP address is used for the Ingress LoadBalancer

  The installation and upgrade scenarios require two static IP addresses for the Control Plane, namely, for the Kubernetes master VIP and for the Ingress LoadBalancer.

• API component is upgraded to address the security fix

• Management of AWS EKS tenant Kubernetes cluster is supported

• IAM auth is integrated with vSphere clusters

• Network configuration step is added to the installer

  The network configuration step enables you to create the Control Plane and tenant network during installation. A master virtual IP address is not required.

• URL of Cisco Container Platform web interface is changed

• Enhanced the Cisco Container Platform web interface:

  • Features

    • Remove master VIP from install wizard

  • Bugfixes

    • Update summary, details, and labels for AWS IAM Role ARNs

    • Update network details to use NetworkModal

    • Fix the invalid form validation case

  • Enhancements

    • Allow networks to be created in dev mode

    • Update labels for CNI choices

  • Styling

    • Include styling fixes for the top navigation bar during narrow page width

  • Refactoring

    • Rename EKS 'config' to 'provider'

  • i18n

    • Fix bug with JS locale pathname

    • Add base support for i18n

For step by step instructions on installing Cisco Container Platform, refer to the Cisco Container Platform Installation Guide.

• Upgrading Cisco Container Platform is supported from the 1.0.0 release for deployments using Calico or ACI for CNI.

• If an existing deployment uses Contiv for CNI, then upgrades to the 2.2.2 version is not supported.

• Patched the authentication token security fix

• Patched CVE-2018-1002105 by upgrading to Kubernetes 1.10.11 and 1.11.5.

• Fixed time synchronization issue on nodes

• Cisco Container Platform web interface bug fixes

• NTP settings

• Rebooting the Cisco Container Platform installer enables you to retry a failed Cisco Container Platform installation.

• After an upgrade, the control plane web interface URL is a combination of the master node virtual IP address and the port number. But, for a new control plane instance, the URL to its web interface is a fixed IP address.

• Cisco Container Platform must use a Kubernetes 1.10 or 1.11 image that is associated with this release. Older versions of the tenant base image are not supported.

• ACI tenant cluster does not work with a link-local interface with Kubernetes 1.11.3.

• You can use only the latest two versions of the tenant image that are associated with the current release. Use of older versions of the tenant image is not supported.

• You will get errors when you scale up tenant clusters or add new node pools to clusters that were created using an older version of Cisco Container Platform.

  Workaround

  You must upgrade Cisco Container Platform before attempting to scale up tenant clusters or add new node pools.

• Kubernetes 1.11.3 API server has a known memory leak issue

• When using HyperFlex as the dynamic provisioner, mounting volumes may fail with the following error message:

  MountVolume.SetUp failed for volume "xxxxx" : mount command failed, status: Failed to mount volume xxxxx, reason:

  Workaround

  1. Restart the scvmclient on the esx server using the following command:

     /etc/init.d/scvmclient restart

  2. Ensure that the status is running.

• Contiv as the CNI for tenant clusters is only supported as Tech Preview, and upgrading to a newer version of Cisco Container Platform is not supported.

• In an ACI environment, the link to a tenant cluster Kubernetes Dashboard from the Cisco Container Platform dashboard is not supported. To view the tenant cluster in the Kubernetes Dashboard, you need to obtain the Ingress IP of external IP address using kubectl get svc.

• The Cisco Container Platform web interface displays links to external pages such as Smart Licensing. You cannot launch these pages if you do not have access to them.

• Virtual IP address is not released when cluster creation fails.

• In a Contiv deployment, you should not use matchExpressions for a NetworkPolicy.

• In a Contiv deployment, network policy does not work with the hostnetwork pod.

• In a Contiv deployment, various networks are used internally by Contiv, and communication to IP addresses outside the cluster is blocked if there is an overlap.

• In a Calico deployment:

  • The network policy matching on labels will not block hostnetwork access to pods or services.

  • Host IP change may impact pod networking. To resolve the issue, you need to restart the Calico pods.

• istioctl is not installed when you enable Istio. You can follow the Cisco Container Platform documentation to install istioctl.

• When upgrading Istio from the 0.8 version to the 1.0 version, the backend services stop responding and you need to manually restart them.

• A master VIP is required for a tenant cluster upgrade. Creating tenant clusters using an API without specifying a master VIP has a risk of corrupting the tenant cluster during tenant cluster upgrades.

• When you upgrade tenant clusters the Prometheus and EFK components are purged before installing the new versions. If you want to save history, a manual backup and migration is required before a tenant cluster upgrade.

• After an upgrade, the Cisco Container Platform web interface port may be different from the previous version.

• Taking a snapshot of the VMs managed by Cisco Container Platform is currently unsupported and results in failures during upgrades.

• ACI deployments are only supported in online mode.

• ACI deployments do not support Kubernetes security context.