Releases: vmware-archive/admiral
vic_v1.5.6
What's in the Release Notes
- New Features
- Download Binaries
- Installation and Upgrade
- Documentation
- Resolved Issues
- Known Issues
- Open Source Components
New Features
This release provides the bug fixes listed under Resolved Issues below.
Download Binaries
Official VMware vSphere Integrated Containers 1.5.6 release: http://www.vmware.com/go/download-vic
Open-source Admiral project: an Admiral container image is available on Docker Hub.
Installation and Upgrade
- For instructions about how to deploy open-source Admiral, see the Admiral Wiki.
- For instructions about how to deploy and upgrade the vSphere Integrated Containers appliance, see Deploy the vSphere Integrated Containers Appliance and Upgrade the vSphere Integrated Containers Appliance.
Documentation
- For details on using open-source Admiral, see the Admiral Wiki.
- For details on how to use vSphere Integrated Containers, see https://vmware.github.io/vic-product/assets/files/html/1.5/.
Resolved Issues
- TLS v1.1 is no longer supported.
Known Issues
None at time of writing.
Open Source Components
The copyright statements and licenses applicable to the open source software components distributed in vSphere Integrated Containers / Admiral are available in the LICENSE file.
vic_v1.5.5
What's in the Release Notes
- New Features
- Download Binaries
- Installation and Upgrade
- Documentation
- Resolved Issues
- Known Issues
- Open Source Components
New Features
This release provides the bug fixes listed under Resolved Issues below.
Download Binaries
Official VMware vSphere Integrated Containers 1.5.5 release: http://www.vmware.com/go/download-vic
Open-source Admiral project: an Admiral container image is available on Docker Hub.
Installation and Upgrade
- For instructions about how to deploy open-source Admiral, see the Admiral Wiki.
- For instructions about how to deploy and upgrade the vSphere Integrated Containers appliance, see Deploy the vSphere Integrated Containers Appliance and Upgrade the vSphere Integrated Containers Appliance.
Documentation
- For details on using open-source Admiral, see the Admiral Wiki.
- For details on how to use vSphere Integrated Containers, see https://vmware.github.io/vic-product/assets/files/html/1.5/.
Resolved Issues
- Fix issue causing Project admins not to be able to edit templates.
- Fix issue authenticating against some private docker registries.
- Fix issue causing deleted VCH to stay in ON state.
Known Issues
None at time of writing.
Open Source Components
The copyright statements and licenses applicable to the open source software components distributed in vSphere Integrated Containers / Admiral are available in the LICENSE file.
vic_v1.5.4
What's in the Release Notes
- New Features
- Download Binaries
- Installation and Upgrade
- Documentation
- Resolved Issues
- Known Issues
- Open Source Components
[VBV-2942] Bump Admiral to 1.5.4
Change-Id: Ib90b3028971862098978bebb38559bad4b0f842b
Reviewed-on: https://bellevue-ci-gerrit.eng.vmware.com:443/c/85044
Closures-Verified: jenkins <[email protected]>
Upgrade-Verified: jenkins <[email protected]>
CS-Verified: jenkins <[email protected]>
PG-Verified: jenkins <[email protected]>
Bellevue-Verified: e_vcoauto_glob_1 <[email protected]>
Reviewed-by: Lazarin Lazarov <[email protected]>
New Features
This release provides the bug fixes listed under Resolved Issues below.
Download Binaries
Official VMware vSphere Integrated Containers 1.5.4 release: http://www.vmware.com/go/download-vic
Open-source Admiral project: an Admiral container image is available on Docker Hub.
Installation and Upgrade
- For instructions about how to deploy open-source Admiral, see the Admiral Wiki.
- For instructions about how to deploy and upgrade the vSphere Integrated Containers appliance, see Deploy the vSphere Integrated Containers Appliance and Upgrade the vSphere Integrated Containers Appliance.
Documentation
- For details on using open-source Admiral, see the Admiral Wiki.
- For details on how to use vSphere Integrated Containers, see https://vmware.github.io/vic-product/assets/files/html/1.5/.
Resolved Issues
None.
Known Issues
None at time of writing.
Open Source Components
The copyright statements and licenses applicable to the open source software components distributed in vSphere Integrated Containers / Admiral are available in the LICENSE file.
vic_v1.5.3
What's in the Release Notes
- New Features
- Download Binaries
- Installation and Upgrade
- Documentation
- Resolved Issues
- Known Issues
- Open Source Components
New Features
This release provides the bug fixes listed under Resolved Issues below.
Download Binaries
- Official VMware vSphere Integrated Containers 1.5.3 release: http://www.vmware.com/go/download-vic
- Open-source Admiral project: an Admiral container image is available on Docker Hub.
Installation and Upgrade
- For instructions about how to deploy open-source Admiral, see the Admiral Wiki.
- For instructions about how to deploy and upgrade the vSphere Integrated Containers appliance, see Deploy the vSphere Integrated Containers Appliance and Upgrade the vSphere Integrated Containers Appliance.
Documentation
- For details on using open-source Admiral, see the Admiral Wiki.
- For details on how to use vSphere Integrated Containers, see https://vmware.github.io/vic-product/assets/files/html/1.5/.
Resolved Issues
- Fix issue ignoring registry.no.proxy.list property and routing connections to registries through the proxy.
- Fix issue with 'Publish All Ports' option always forced to true
Known Issues
None at time of writing.
Open Source Components
The copyright statements and licenses applicable to the open source software components distributed in vSphere Integrated Containers / Admiral are available in the LICENSE file.
vic_v1.5.2
What's in the Release Notes
- New Features
- Download Binaries
- Installation and Upgrade
- Documentation
- Resolved Issues
- Known Issues
- Open Source Components
New Features
This release provides the bug fixes listed under Resolved Issues below.
Download Binaries
- Official VMware vSphere Integrated Containers 1.5.2 release: http://www.vmware.com/go/download-vic
- Open-source Admiral project: an Admiral container image is available on Docker Hub.
Installation and Upgrade
- For instructions about how to deploy open-source Admiral, see the Admiral Wiki.
- For instructions about how to deploy and upgrade the vSphere Integrated Containers appliance, see Deploy the vSphere Integrated Containers Appliance and Upgrade the vSphere Integrated Containers Appliance.
Documentation
- For details on using open-source Admiral, see the Admiral Wiki.
- For details on how to use vSphere Integrated Containers, see https://vmware.github.io/vic-product/assets/files/html/1.5/.
Resolved Issues
- Fix an issue when adding new hosts from the Administration tab. The host was added always to the default project.
- Increase the limit of the SAML token, so users who are members of a lot of groups can log in.
Known Issues
None at time of writing.
Open Source Components
The copyright statements and licenses applicable to the open source software components distributed in vSphere Integrated Containers / Admiral are available in the LICENSE file.
vic_v1.5.0
What's in the Release Notes
- New Features
- Download Binaries
- Installation and Upgrade
- Documentation
- Resolved Issues
- Known Issues
- Open Source Components
New Features
This release provides the bug fixes listed under Resolved Issues below.
Download Binaries
- Official VMware vSphere Integrated Containers 1.5.0 release: http://www.vmware.com/go/download-vic
- Open-source Admiral project: an Admiral container image is available on Docker Hub.
Installation and Upgrade
- For instructions about how to deploy open-source Admiral, see the Admiral Wiki.
- For instructions about how to deploy and upgrade the vSphere Integrated Containers appliance, see Deploy the vSphere Integrated Containers Appliance and Upgrade the vSphere Integrated Containers Appliance.
Documentation
- For details on using open-source Admiral, see the Admiral Wiki.
- For details on how to use vSphere Integrated Containers, see https://vmware.github.io/vic-product/assets/files/html/1.5/.
Resolved Issues
- Improved error handling when adding new cluster and deleting projects
- Fix in parallel filtering and completion of tasks
- Fix referer header when making outgoing calls to be the public uri
- Photon version set to 2.0
- Angular version set to 6
Known Issues
None at time of writing.
Open Source Components
The copyright statements and licenses applicable to the open source software components distributed in vSphere Integrated Containers / Admiral are available in the LICENSE file.
vic_v1.4.3
What's in the Release Notes
- New Features
- Download Binaries
- Installation and Upgrade
- Documentation
- Resolved Issues
- Known Issues
- Open Source Components
New Features
This release provides the bug fixes listed under Resolved Issues below.
Download Binaries
- Official VMware vSphere Integrated Containers 1.4.3 release: http://www.vmware.com/go/download-vic
- Open-source Admiral project: an Admiral container image is available on Docker Hub.
Installation and Upgrade
- For instructions about how to deploy open-source Admiral, see the Admiral Wiki.
- For instructions about how to deploy and upgrade the vSphere Integrated Containers appliance, see Deploy the vSphere Integrated Containers Appliance and Upgrade the vSphere Integrated Containers Appliance.
Documentation
- For details on using open-source Admiral, see the Admiral Wiki.
- For details on how to use vSphere Integrated Containers, see https://vmware.github.io/vic-product/assets/files/html/1.4/.
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.
docker execalways returns 0 and ignores the exit code of processes. vic/#5692docker execalways returns 0, even if you specify-it. This issue is potentially due to a delay in vSphere host synchronization. If you configure command-based health checks in vSphere Integrated Containers Management Portal, the health checks are always successful for containers that are provisioned on affected VCHs, even if the user-specified command does not exist in the scope of the container. This is because command-based health checks are considered to be successful if the exit code of that command is 0.
Known Issues
None at time of writing.
Open Source Components
The copyright statements and licenses applicable to the open source software components distributed in vSphere Integrated Containers / Admiral are available in the LICENSE file.
v1.4.1
What's in the Release Notes
- New Features
- Download Binaries
- Installation and Upgrade
- Documentation
- Resolved Issues
- Known Issues
- Open Source Components
New Features
This release provides the following new feature:
- New Built-In Repositories view in vSphere Integrated Containers Management Portal provides better visibility on all repositories that reside in the vSphere Integrated Containers Registry.
Download Binaries
- Official VMware vSphere Integrated Containers 1.4.1 release: http://www.vmware.com/go/download-vic
- Open-source Admiral project: an Admiral container image is available on Docker Hub.
Installation and Upgrade
- For instructions about how to deploy and upgrade the vSphere Integrated Containers appliance, see Deploy the vSphere Integrated Containers Appliance and Upgrade the vSphere Integrated Containers Appliance.
- For instructions about how to deploy open-source Admiral, see the Admiral Wiki.
Documentation
- For details on using open-source Admiral, see the Admiral Wiki.
- For details on how to use vSphere Integrated Containers, see https://vmware.github.io/vic-product/assets/files/html/1.4/.
Resolved Issues
None at time of writing.
Known Issues
docker execalways returns 0 and ignores the exit code of processes. vic/#5692docker execalways returns 0, even if you specify-it. This issue is potentially due to a delay in vSphere host synchronization. If you configure command-based health checks in vSphere Integrated Containers Management Portal, the health checks are always successful for containers that are provisioned on affected VCHs, even if the user-specified command does not exist in the scope of the container. This is because command-based health checks are considered to be successful if the exit code of that command is 0.
Open Source Components
The copyright statements and licenses applicable to the open source software components distributed in vSphere Integrated Containers / Admiral are available in the LICENSE file.
v1.4.0
What's in the Release Notes
- New Features
- Download Binaries
- Installation and Upgrade
- Documentation
- Resolved Issues
- Known Issues
- Open Source Components
New Features
This release provides the following new features and enhancements:
- Added project level registries in vSphere Integrated Containers Management Portal managed by DevOps admins.
- Enforced whitelist registry mode that allows search and provision only within registries added as global or project registries in vSphere Integrated Containers Management Portal.
- Added a namespace concept so that administrators can only allow certain namespaces of a given registry when adding new registries.
- General UI and usability improvements.
- Bug fixes listed in Resolved Issues below.
Download Binaries
- Official VMware vSphere Integrated Containers 1.4.0 release: http://www.vmware.com/go/download-vic
- Open-source Admiral project: an Admiral container image is available on Docker Hub.
Installation and Upgrade
- For instructions about how to deploy and upgrade the vSphere Integrated Containers appliance, see Deploy the vSphere Integrated Containers Appliance and Upgrade the vSphere Integrated Containers Appliance.
- For instructions about how to deploy open-source Admiral, see the Admiral Wiki.
Documentation
- For details on using open-source Admiral, see the Admiral Wiki.
- For details on how to use vSphere Integrated Containers, see https://vmware.github.io/vic-product/assets/files/html/1.4/.
Resolved Issues
The following issues documented as known issues in previous versions have been fixed in 1.4.0:
None at time of writing.
Known Issues
docker execalways returns 0 and ignores the exit code of processes. vic/#5692docker execalways returns 0, even if you specify-it. This issue is potentially due to a delay in vSphere host synchronization. If you configure command-based health checks in vSphere Integrated Containers Management Portal, the health checks are always successful for containers that are provisioned on affected VCHs, even if the user-specified command does not exist in the scope of the container. This is because command-based health checks are considered to be successful if the exit code of that command is 0.
Open Source Components
The copyright statements and licenses applicable to the open source software components distributed in vSphere Integrated Containers / Admiral are available in the LICENSE file.
v1.3.0
Docker hub image: https://hub.docker.com/r/vmware/admiral/ v1.3.0
If you are looking for the latest VIC release at the moment, check the release vic_v1.3.0.
Resolved Issues
Various bug fixes and improvements.
Known Issues
No known issues at the time of writing.
Installation
- For instructions about how to deploy open-source Admiral, see the Admiral Wiki.