Skip to content

vSphere Integrated Containers Appliance v1.4.3
Compare
Choose a tag to compare
@DanielXiao DanielXiao released this 17 Sep 02:19
· 480 commits to master since this release
v1.4.3
deedb98
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

What's in the Release Notes

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.3-6240-deedb985.ova

Filesize (vic-v1.4.3-6240-deedb985.ova) = 3407800320
SHA256 (vic-v1.4.3-6240-deedb985.ova) = 914d373fca75fbccd76dfb53a9939910e120466c5e944f8a50ce190c56000c34
SHA1 (vic-v1.4.3-6240-deedb985.ova) = ae672f81a4ecbd9a041b98ea33f7f0614b1676b6
MD5 (vic-v1.4.3-6240-deedb985.ova) = dac10f8eab16f52e5429a1cbdb15a36f

This OVA contains the following component versions:

--admiral v1.4.3 \
--harbor https://storage.googleapis.com/harbor-releases/harbor-offline-installer-v1.5.3.tgz  \
--vicengine https://storage.googleapis.com/vic-engine-releases/vic_v1.4.3.tar.gz \
--vicmachineserver v1.4.3
--vicui https://storage.googleapis.com/vic-ui-releases/vic_ui_v1.4.3.tar.gz

Installation and Upgrade

IMPORTANT: If you use vSphere 6.7 update 1 or later, you must use vSphere Integrated Containers 1.4.3 or later. 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 do not work with that version.

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.

Changes

Full list of changes from 1.4.2.

New Features

vSphere Integrated Containers 1.4.3 includes the following new features:

  • Automatic installation or upgrade of the vSphere Integrated Containers plug-in for the vSphere Client during deployment and upgrade of the appliance. Read more.
  • Added VM-Host Affinity option to the Create Virtual Container Host wizard. Read more.
  • Added vic-machine create --no-proxy option to skip proxying for certain URLs or domains. Read more.
  • Added shell auto-complete function to vic-machine. Read more.

Enhancements

vSphere Integrated Containers 1.4.3 includes the following improvements:

  • Added vCenter Server thumbprint verification to the initialization process during deployment and upgrade of the appliance, to improve security. Read more.
  • Added appliance address and version information in the vSphere Integrated Containers plug-in for the vSphere Client. Read more.
  • Improved the specification of a routing destination and gateway for the management network in the Create Virtual Container Host wizard. Read more.
  • Added VM ID to the output of vic-machine create and inspect. Read more.
  • Removed UI packages from vSphere Integrated Containers Engine bundle. Read more.
  • 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.4.3.

  • Using FQDN when generating certificates for 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.

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

Known Issues

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

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:

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.

Assets 2
Loading