MKE 3.5.3 issues for which there are available workaround solutions include:
[FIELD-4200] Reloading firewalld can disable docker ingress routing mesh
[MKE-8538] Limited Windows support dump availability¶
Only limited support dumps are available on Windows worker nodes.
Manually collect the Windows worker node logs.
[FIELD-4200] Reloading firewalld can disable docker ingress routing mesh¶
firewalld-policy init container can disable the
docker ingress routing mesh when reloading
Prevent the issue from recurring by disabling
sudo systemctl disable --now firewalld
Restore missing iptables chains by restarting
sudo systemctl restart docker
dockerdstops all containers on the corresponding node. The node capacity will not be available to the cluster until the node returns to a healthy state in MKE. You must restart
dockerdon manager nodes one node at a time, confirming the health of each one in MKE before moving on to the next.
Confirm issue resolution by checking for the presence of the
sudo iptables --list DOCKER-INGRESS
Chain DOCKER-INGRESS (2 references) target prot opt source destination [...]