Addressed issues¶
Issues that have been addressed in the MKE 3.5.4 release include:
[FIELD-4820, FIELD-4893] Fixed an issue wherein the output of the
docker ps
anddocker inspect
MKE endpoints included duplicate port entries.[FIELD-4871] Fixed an issue wherein Services could not be filtered by the required Stack.
[FIELD-4868] Fixed an issue wherein MKE could report an incorrect healthy container count.
[FIELD-4788] Fixed an issue wherein MKE failed to uninstall when running in Swarm-only mode.
[FIELD-4757] Fixed an issue with the MKE web UI wherein the logs did not display for Pods with multiple containers.
[FIELD-4271] Fixed an issue with the MKE web UI wherein various columns could not be sorted in the Nodes and Containers tables.
[FIELD-4200] Fixed an issue wherein the
DOCKER-INGRESS
chain could get lost when firewalld is running.[FIELD-4158] Fixed an issue with the MKE web UI wherein Pods erroneously displayed as Not Ready.
[MKE-8538] Fixed an issue wherein only limited support dumps were available on Windows nodes.
[MKE-8944] Fixed an issue wherein locked accounts remained locked when the account password was changed by an administrator.
[MKE-8886] Fixed an issue with the MKE web UI wherein a RethinkDB error banner contained a broken link to the product documentation.
[FIELD-2778] Fixed an issue wherein Windows nodes that were added to an MKE cluster with docker swarm join using a manager token were demoted to worker nodes in the cluster.
[FIELD-4873] Fixed an issue with MKE clusters running on Ubuntu 20.04 wherein MKE failed to encrypt traffic when IPSec was enabled.