This is a known issue affecting Admiral and there is currently no resolution.
Workaround:
A VIC Appliance patch has been created to workaround this issue which involves the following:
- Creation of admiral-proxy systemd service, with associated configuration and start/cleanup scripts, located in /etc/vmware/admiral folder
- Modification of configure_admiral.sh script, to remove the management of custom.conf file (Admiral custom configuration file, especially for the proxy settings, but not only)
- Modification of admiral service, to wait after admiral-proxy service to have started, due to configuration of the custom.conf file managed by admiral-proxy now.
- Docker image for admiral-proxy.
- Automated creation of certificate folder in /storage/data/admiral/proxy_certs for SSL Termination certificate.
- Installer script for ease of deployment.
This solution consists of deploying an Anonymous Proxy Container, to which Admiral will connect to. In turn, this Container will pass the request to the Corporate Proxy with Authentication.
In order to install the patched VIC Appliance, open a Support Request asking for VIC Appliance proxy patch.