What's in the Release Notes
- Download
- Installation and Upgrade
- Using vSphere Integrated Containers
- Changes
- 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.5.3-7511-ba6b1644.ova
File size: 2478755840
SHA256 checksum: f7559a655d460a11751dffdb299157e62cc2955c1fbbb977e595d340b58bced7
SHA1 checksum: d938bf19ff3c8843da2fededc923074a38e42a11
MD5 checksum: f426f65903d47a552ac36f110fd7533e
This OVA contains the following component versions:
- Appliance: https://github.com/vmware/vic-product/archive/v1.5.3.zip
- Engine: https://github.com/vmware/vic/archive/v1.5.3.zip
- Harbor: https://github.com/goharbor/harbor/archive/v1.7.5.zip
- Admiral: https://github.com/vmware/admiral/archive/vic_v1.5.3.zip
- Client Plug-In: https://github.com/vmware/vic-ui/archive/v1.5.3.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.
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
New Features
vSphere Integrated Containers 1.5.3 includes the following new features:
- Support for vCenter Server versions 6.7 up to and including 6.7 update 2. Read more.
- Support for NSX-T Data Center version 2.4. Read more.
- New option to reconfigure the appliance settings to change the TLS certificates after you have deployed it. Read more.
- Support for FQDN of the old version of the appliance in the upgrade script. Read more.
- Option to configure the path to an existing
ca.pemfile in thevic-machine configurecommand. Read more. - Option to forward appliance logs to Syslog servers. Read more.
- Option to roll back the VCH configuration changes to the previous settings. Read more.
- The
--registry-caoption of the thevic-machine configurecommand replaces certificates instead of just adding them. Read more. - Increases the length of the root password to 128 characters. Read more.
- Option to click on the vSphere Integrated Containers appliance IP address in the vSphere Integrated Containers Summary tab to go to the vSphere Integrated Containers Getting Started page. Read more.
Enhancements
vSphere Integrated Containers Engine 1.5.3 includes the bug fixes listed in Resolved Issues below.
Resolved Issues
The following issues that were documented as known issues in previous releases or reported by customers have been fixed in v1.5.3:
- Cannot browse default-vic-registry when Proxy is set. PR 2478
- 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.
Full list of changes from 1.5.2.
See also the resolved issues for each of the vSphere Integrated Containers components:
- vSphere Integrated Containers Engine
- vSphere Integrated Containers Management Portal
- vSphere Integrated Containers Registry
- vSphere Integrated Containers Plug-In for vSphere Client
Known Issues
vSphere Integrated Containers appliance 1.5.3 has the same known issues as v1.5.2.
Appliance services are not available if accessed through NAT or a reverse proxy. #1172 Workaround: Add the FDQN by which the appliance identifies itself to the vSphere Client shows warnings when you attempt legitimate operations on the appliance VM. #1184 Workaround: Ignore the warnings and click Yes to proceed with the operation.
View all
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.
/etc/hosts file of the client machine, pointing to the translated IP address that the client sees.
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.
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 Registry
- 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.