1.2.0
Changelog
Fixes
- Wait for MSR healthy state after upgrading engine
- Fix MKE image listing for Windows targets
- Fix MKE image listing for SELinux enabled hosts
- Fix MKE/MSR
-tpX
pre-release version number sorting - Fix log files being created as executables
- Fix panic in Install MSR phase when no
spec.msr
defined in configuration - Fix RHEL MCR configuration when SELinux enabled
- Mount
docker.sock
when listing MKE images - Use
$ProgressPreference=SilentlyContinue
and-NoProfile
when running PowerShell commands on Windows targets - Fix --accept-license when using the launchpad register subcommand
- Add non-root user to "docker" group and run docker commands without sudo
Product default versions
- Set default
spec.mke.version
to 3.3.7 - Set default
spec.msr.version
to 2.8.5 - Set default
spec.mcr.version
to 20.10.0
New supported target operating systems
- Add support for Ubuntu 20.04 targets
- Add support for SLES targets
- Add support for Oracle Linux targets
Configuration API changes
- New API version
launchpad.mirantis.com/mke/v1.3
(automatic migration from any earlier version) - Add
spec.mke.swarmInstallFlags
andspec.mke.swarmUpdateCommands
for customization of swarm installation - Add
spec.mke.upgradeFlags
for setting additional flags to MKE upgrade command - Add
spec.msr.upgradeFlags
for setting additional flags to MSR upgrade command - Connection address moved from host level to protocol settings (
spec.hosts[*].address
=>spec.hosts[*].ssh.address
)
CLI changes
- Global flags like
--debug
are expected after the last subcommand (launchpad apply --debug
instead oflaunchpad --debug apply
) - Allow disabling in-phase cleanup (ie. use
docker run
without--rm
) for investigating apply failures - More descriptive error messages when client bundle PEM decoding fails
Configuration API changes
The new configuration API version launchpad.mirantis.com/mke/v1.3
adds a couple of fields and changes where the connection address is defined.
Configuration migration
When not using any of the new fields, a configuration using any of the older configuration API versions will still work, but warnings will be displayed.
If you want to output a new configuration migrated to the new API version, you can use:
$ launchpad describe config --config launchpad.yaml > new.yaml
The connection address is now defined under the connection protocol settings:
Before:
apiVersion: launchpad.mirantis.com/mke/v1.1
kind: mke
spec:
hosts:
- role: manager
address: 10.0.0.1
ssh:
port: 8022
Now:
apiVersion: launchpad.mirantis.com/mke/v1.3
kind: mke
spec:
hosts:
- role: manager
ssh:
address: 10.0.0.1
port: 8022