Windows pods are in crashloopback about sig-windows-dev-tools HOT 12 CLOSED

this is probably my fault, i copy/pasted the wrong windows YAML from the internet :)

from sig-windows-dev-tools.

I think this issue is effectively resolved and we've moved onto having other issues related to the windows networking; I think this can be closed. Right?

from sig-windows-dev-tools.

@knabben .... lets get rid of this ServiceMonitor nonsense ?

from sig-windows-dev-tools.

Lets use this pattern sais @jsturtevant ,... but DONT USE THIS IMAGE , use IIS ?
https://github.com/jsturtevant/windows-k8s-playground/blob/master/deployments/iis/iis-prewarm.yaml

maybe ?

from sig-windows-dev-tools.

/assign

from sig-windows-dev-tools.

@knabben is there something I can do to help on this? I was just about to report this same issue as I was working on the sonobuoy integration.

from sig-windows-dev-tools.

@johnSchnake I'm trying a few images without servicemonitor.exe if you have one more stable feel free to replace the one we have in the yaml

from sig-windows-dev-tools.

So I'm trying to just "fix" the existing code and found 2 things of note:

• 1. The version of servicemonitor that was specified did not exist on the downloads page for some reason (https://github.com/microsoft/IIS.ServiceMonitor/releases)
• 2. After updating it to an existing release I still got the same error. However, from the NODE it worked so I think something is wrong with the networking on the pod.

 Invoke-WebRequest -UseBasicParsing -Uri 'https://dotnetbinaries.blob.core.windows.net/servicemonitor/2.0.1.9/ServiceMonitor.exe'
...
StatusCode        : 200
StatusDescription : OK

Maybe ya'll already knew that was the case, but it seemed like progress to me. It seems to me that if we cut out the servicemonitor then maybe the iis server will start up but perhaps all the windows nodes will still be effectively broken.

from sig-windows-dev-tools.

https://stackoverflow.com/questions/60885492/cant-access-internet-from-within-windows-gke-pod says that MAC spoofing needs to be enabled but I'm out of my norm here and unsure if this is something to be done at the virtualbox/vagrant/windows level.

Am I off base here or does this seem like a trail to follow?

from sig-windows-dev-tools.

We agreed in the last sig-windows pair to change the image here to the official IIS, instead of changing the command of the current YAML.

Probably a better try IMO. We could go with: https://hub.docker.com/_/microsoft-windows-servercore-iis

from sig-windows-dev-tools.

yes, we changed the pod spec.

/close

from sig-windows-dev-tools.

@knabben: Closing this issue.

from sig-windows-dev-tools.