Addressed issues

The following issues have been addressed in the Mirantis Container Cloud release 2.20.0 along with the Cluster releases 11.4.0 and 7.10.0:

  • [25476] Fixed the timeout behavior to avoid Keepalived and HAProxy check failures.

  • [25076] Fixed the remote_syslog configuration. Now, you can optionally define SSL verification modes. For details, see StackLight configuration parameters: Logging to syslog.

  • [24927] Fixed the issue wherein a failure to create lcmclusterstate did not trigger a retry.

  • [24852] Fixed the issue wherein the Upgrade Schedule tab in the Container Cloud web UI was displaying the NOT ALLOWED label instead of ALLOWED if the upgrade was enabled.

  • [24837] Fixed the issue wherein some Keycloak iam-keycloak-* pods were in the CrashLoopBackOff state during an update of a baremetal-based management or managed cluster with enabled FIPs.

  • [24813] Fixed the issue wherein the IPaddr objects were not reconciled after the ipam/SVC-* labels changed on the parent subnet. This prevented the ipam/SVC-* labels from propagating to IPaddr objects and caused the serviceMap update to fail in the corresponding IpamHost.

  • [23125] Fixed the issue wherein an OpenStack-based regional cluster creation in an offline mode was failing. Adding the Kubernetes load balancer address to the NO_PROXY environment variable is no longer required.

  • [22576] Fixed the issue wherein provisioning-ansible did not use the wipe flags during the deployment phase.

  • [5238] Improved the Bastion readiness checks to avoid issues with some clusters having several Bastion nodes.