Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Ingress will not start on Windows 2019 worker nodes

See original GitHub issue

I’m currently running MicroK8s version 2.1.0 on Windows 10 Enterprise (ver: 21H1, Build: 19043.1237). I have a Windows Server 2019 (Ver: 1809. Build: 17763.1577) VM connected as a worker. When trying to run either microk8s.exe enable ingress or microk8s.exe enable traefik, the ingress pod is able to start on the Linux worker node, but is unable to start on the Windows worker. In the case of both addons ingress and traefik the issue was because no windows container image was able to be retrieved.

After playing a bit, I was able to get the traefik ingress controller to work, but I had to perform the following steps to get it to work:

(on windows worker): docker network create -d nat host
(on windows worker): docker pull traefik:v2.3.0-windowsservercore-1809
(on windows worker): docker tag 9fddb6b884a3 traefik:2.3
(on host machine): microk8s.exe enable traefik

I feel that my workaround is not the correct way to have gotten the Traefik ingress controller to work. And as of now, I have not been able to get the addon called ingress to work at all.

Can I ask for some guidance on what I’m doing wrong here?

inspection-report-20210926_205618.tar.gz

Issue Analytics

State:
Created 2 years ago
Comments:6 (3 by maintainers)

Top GitHub Comments

1reaction

mkazmierczykcommented, Jan 20, 2022

Hi,

Did you manage to find any solution for described problem ? It exists for ingress addon and openebs addon.

I have mixed cluster with Linux nodes and Windows workers. By default MicroK8s tries to create ingress controller on every worker but on Windows it failes. The same is for Openebs that as addon doesn’t have node affinity and k9s tries to start its conteiners on Windows workers what results they fail.

1reaction

ktsakalozoscommented, Sep 27, 2021

The issue we have is that the manifests used to deploy the ingress daemonsets are not multi-arch. We usually expect the image references to support multiple architectures [1]. For example, the traefik 2.5.3 image [2] if for amd64, arm64 and arm but not for windows.

I am not sure what the right path forward is in this case. @balasu, @balchua @joedborg any ideas?

[1] https://kubernetes.io/docs/concepts/containers/images/#multi-architecture-images-with-image-indexes [2] https://hub.docker.com/_/traefik?tab=tags&page=1&ordering=last_updated