vSphere Integrated Containers Appliance v1.5.0
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.0-6915-e18e6647.ova
File size: 2524979200
SHA256 checksum: 183c68214b7c9fdbfaf619cd6a368fd3a2500a9d518ce2b9fd2e14e991445b82
SHA1 checksum: 6f0c6931807da2bc915836f6ae1ff7e0a407599a
MD5 checksum: 13cecb6068bef241fafff6d04d55462c
This OVA contains the following component versions:
Appliance: https://github.com/vmware/vic-product/archive/v1.5.0.zip
Engine: https://github.com/vmware/vic/archive/v1.5.0.zip
Registry: https://github.com/goharbor/harbor/archive/v1.7.1.zip
Management Portal: https://github.com/vmware/admiral/archive/vic_v1.5.0.zip
UI: https://github.com/vmware/vic-ui/archive/v1.5.0.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
Full list of changes from 1.4.4.
New Features
vSphere Integrated Containers 1.5.0 includes the following new features:
- Support for the use of NSX-T Data Center logical switches for all VCH networks. Read more.
- Support for the use of an alternative Linux kernel ISO from which to boot container VMs. Read more.
- Upgraded the OS of all vSphere Integrated Containers components to Photon OS 2.0. Read more.
- Addition of the
--storage-quota
option tovic-machine create
andconfigure
, to set a limit on the amount of storage that a VCH can consume. Read more.
Enhancements
vSphere Integrated Containers 1.5.0 includes the following enhancements:
- Addition of an option to specify an NTP server during deployment of the vSphere Integrated Containers appliance. Read more.
- New requirement to enter the appliance root password during initialization, reinitialization, and upgrade of the appliance. Read more.
- Added
COMPOSE_TLS_VERSION
in theenv
file that is generated during VCH deployment. Read more. - Security and bug fixes listed in Resolved Issues below.
Resolved Issues
No issues that were documented as known issues in previous releases have been fixed in vSphere Integrated Containers appliance 1.5.0. See 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.0 has the same known issues as v1.4.4.
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 bySolution 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 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.