What's in the Release Notes
- Download
- Installation and Upgrade
- Using vSphere Integrated Containers
- Changes
- Known Issues
- Open Source Components
Download
Download location: https://storage.googleapis.com/vic-product-ova-releases/vic-v1.4.1-rc2-5496-f2fdac75.ova
This OVA contains the following component versions:
--admiral v1.4.1-rc2 \
--harbor https://storage.googleapis.com/harbor-releases/harbor-offline-installer-v1.5.1.tgz \
--vicengine https://storage.googleapis.com/vic-engine-releases/vic_v1.4.1-rc2.tar.gz \
--vicmachineserver v1.4.1-rc2
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.0.
New Features
This release includes the bug fixes and enhancements listed below.
Enhancements
See the enhancements for the following vSphere Integrated Containers components:
Resolved Issues
See the resolved issues for each of the vSphere Integrated Containers components:
- vSphere Integrated Containers Engine
- vSphere Integrated Containers Registry
- vSphere Integrated Containers Management Portal
- vSphere Integrated Containers Plug-In for vSphere Client
Additionally, the following other issues have been addressed:
- The OVF now uses the VMXNET3 adapter. #1746
Previously, the E1000 adapter was used. - The OVF now uses distinct property keys for registry and management ports. #1642
Previously, the OVF used similar keys for the registry and management ports causing a collision when deploying via the vSphere H5 client. (Note: please refer to the vSphere documentation for information about which vSphere H5 Client versions support deployment of OVAs.)
Known Issues
- Harbor upgrade fails when upgrading from v1.4.0 vmware/harbor#5218
The Harbor database is not copied from the old OVA when upgrading using the automated upgrade process introduced in v1.4.0.
With the exception of the resolved issue above, v1.4.1-rc2 also has the same known issues as v1.4.0.
Appliance upgrade script does not support FQDN addresses for the old appliance #1731 Using FQDN when generating certificates for Workaround: Always specify an IP address in the 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.
Deploying the OVA with ovftool results in warnings about file size mismatch. #1166 Workaround: Ignore the error message.
View all
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.
dch-photon results in a <nil> certificate. #925
When generating certificates for use with dch-photon, if you use an FQDN in the -vic-ip parameter the resulting certificate is invalid.
-vic-ip parameter.
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.
If you use ovftool to deploy the appliance, the process ends with the error Wrong file size specified in OVF descriptor for 'vic-disk1.vmdk' and 'vic-disk2.vmdk'. However the deployment succeeds.
See also the known issues for each of the vSphere Integrated Containers components:
- vSphere Integrated Containers Engine
- vSphere Integrated Containers Registry
- 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.