Skip to content

vSphere Integrated Containers UI v1.4.0-rc3

Pre-release
Pre-release
Compare
Choose a tag to compare
@lmalvins lmalvins released this 24 Apr 21:27
· 1 commit to releases/1.4.0 since this release
v1.4.0-rc3
f2088ba
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.

v1.3.1...v1.4.0-rc3

New Features

Stability improvements and bug fixes.

Download Binaries

Open-source vSphere Integrated Containers UI project: https://storage.googleapis.com/vic-ui-releases/vic_ui_v1.4.0-rc3.tar.gz

Installation and Upgrade

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.

NOTE: This documentation is a work-in-progress and has not yet been fully updated for 1.4.0.

Open Source Components

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

Resolved Issues

The following issues that were documented as known issues in previous releases have been fixed in 1.4.0:

  • OVA endpoint appears as null in plug-in when deploying multiple instances of the vSphere Integrated Containers appliance. #365
    The plug-in installer marks only the exact vSphere Integrated Containers appliance that it shipped with as being managed by the plug-in and does not mark any other appliances as such. This can cause some unexpected behaviors such as the OVA endpoint appearing as null if you deploy multiple appliances to the same vCenter Server instance.
  • VCH inventory list and create wizard fails to load when vCenter Server session expires. #228
    If the vCenter server authentication session expires, reloading the VCH inventory list hangs with the error Could not find any VIC appliance VM. Attempts to create a VCH fail with the error Error creating VCH.
  • Plug-in does not appear after successful installation and restart of the vSphere Client services. #299
    If you have successfully installed the plug-in and restarted the vSphere Client services and you do not see the plug-in in the vSphere Client, you might be encountering an SSL certificate mismatch issue. This can occur if the root CA on the vCenter Server Virtual Appliance is updated, either by upgrading to a newer build of vSphere or by running the VMCA Certificate Manager.
  • Plug-in upgrade script incorrectly warns that you are trying to install an older version. #183
    When you run the plug-in upgrade script to upgrade from 1.2.x to 1.3.x, the output warns you that You are trying to install plugins of an older or same version even when you are installing a later version of the plug-in.

Known Issues

The following issues affect the vSphere Integrated Containers plug-in for vSphere Client 1.4.0:

None at time of writing.

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

Assets 2
Loading