vSphere Integrated Containers Appliance v1.4.4

What's in the Release Notes

• Download
• Installation and Upgrade
• Using vSphere Integrated Containers
• Changes
  • New Features
  • Enhancements
  • Resolved Issues
• Known Issues
• Open Source Components

Download

Official vSphere Integrated Containers release: http://www.vmware.com/go/download-vic

Open-source vSphere Integrated Containers project download location: https://storage.googleapis.com/vic-product-ova-releases/vic-v1.4.4-6375-0a6da3d4.ova

File size: 3342868480
SHA256 checksum: 06131aebed1d2fe4299fb9cefcb18d0bc1f2fba4a700660ce94c43f6735f0d93
SHA1 checksum: 1b9dc717225cb0f02bcc2358176cabac8bdc9222
MD5 checksum: 652ebc88cef35cbe1e22207ef41f9287

This OVA contains the following component versions:

Appliance: https://github.com/vmware/vic-product/archive/v1.4.4.zip 
Engine: https://github.com/vmware/vic/archive/v1.4.3.zip 
Registry: https://github.com/goharbor/harbor/archive/v1.5.4.zip 
Management Portal: https://github.com/vmware/admiral/archive/vic_v1.4.3.zip 
UI: https://github.com/vmware/vic-ui/archive/v1.4.4.zip 

Installation and Upgrade

• For instructions about how to deploy the vSphere Integrated Containers appliance, see Deploy the vSphere Integrated Containers Appliance.
• For instructions about how to upgrade an existing vSphere Integrated Containers appliance, see Upgrade the vSphere Integrated Containers Appliance.

IMPORTANT: If you use vSphere 6.7 update 1 or later, you must use vSphere Integrated Containers 1.4.3 or 1.4.4. Due to significant changes in the HTML5 vSphere Client in version 6.7 update 1, previous versions of the vSphere Integrated Containers plug-in for the vSphere Client might not work with that version. Only versions 1.4.3 and 1.4.4 have been verified with vSphere 6.7 update 1.

Using vSphere Integrated Containers

For more details on using vSphere Integrated Containers see the end user documentation at https://vmware.github.io/vic-product/#documentation.

• Overview of vSphere Integrated Containers
• vSphere Integrated Containers for vSphere Administrators
• vSphere Integrated Containers Management Portal Administration
• Using vSphere Integrated Containers as a DevOps Administrator, Developer, or Viewer
• Developing Applications with vSphere Integrated Containers

Changes

Full list of changes from 1.4.3.

New Features

vSphere Integrated Containers 1.4.4 includes no new features.

Enhancements

vSphere Integrated Containers 1.4.4 includes the bug fixes listed in Resolved Issues below.

Resolved Issues

There are no resolved issues in the vSphere Integrated Containers appliance in this release. This release includes fixes for issues that are resolved in new versions of vSphere Integrated Containers Registry and the vSphere Integrated Containers UI:

• vSphere Integrated Containers Registry: Updated Clair to version 2.0.6. This resolves an problem that causes Denial of Service issues with NIST Internet Time Servers getting stuck in a CVE loop. See the Resolved Issues for Harbor 1.5.4.
• vSphere Integrated Containers UI: Fixes issues in the generated vic-machine command in the Create VCH wizard and a UI deployment issue. See the Resolved Issues for vSphere Integrated Containers UI 1.4.4.

Known Issues

With the exception of the resolved issue above, v1.4.4 has the same known issues as v1.4.3.

View all

• Appliance upgrade script does not support FQDN addresses for the old appliance #1731
  When you run the script to upgrade the vSphere Integrated Containers appliance, the script prompts you for the FQDN or IP address of the old version of the appliance. However, the script only supports IP addresses for the appliance, and does not support FQDN addresses. You can use FQDN for vCenter Server addresses.

• Appliance services are not available if accessed through NAT or a reverse proxy. #1172
  The Getting Started page of the appliance includes links to the services running on the appliance. These links are constructed assuming that users connect to the appliance by using its IP or FQDN, and that it is not hidden behind NAT or a reverse proxy.

  Workaround: Add the FDQN by which the appliance identifies itself to the /etc/hosts file of the client machine, pointing to the translated IP address that the client sees.

• vSphere Client shows warnings when you attempt legitimate operations on the appliance VM. #1184
  If you attempt to perform operations on the appliance VM, for example migrate it, move it to a new folder, or restart it, you see a warning that the the VM is managed by Solution vSphere Integrated Containers-H5Client.

  Workaround: Ignore the warnings and click Yes to proceed with the operation.

See also the known issues for each of the vSphere Integrated Containers components:

• vSphere Integrated Containers Engine
• vSphere Integrated Containers Management Portal
• vSphere Integrated Containers Plug-In for vSphere Client

Open Source Components

The copyright statements and licenses applicable to the open source software components distributed in vSphere Integrated Containers are available in the LICENSE file.