David J. M. Karlsen

Check the list of runners at github and forcefully delete them if malfunctioning

@stevespringett Can't we do both? Some will simply not be interested in the licensing altogether and this flag is valuable for those.

Adding the system property seems to work wonders. Thanks!

yes, it works. we have the appgw in another vnet than the cluster, so it only works when running azure-cni, not with kubenet. But that's not related to the version.

@Ikana lambda is a bit strange - that it requires the permissions to be embedded in the resource (the ECR-repo) - have you found any workaround to that? It seems...

Maybe related? https://github.com/kuberhealthy/kuberhealthy/issues/254

> Could you please post logs for the `deployment` pod and the events for the `deployment-deployment` pod? I'll wait for one to hang. Just cleared them out today. > What...

here's one ``` iority: 0 Node: alt-ksx-r-c01oco03/139.114.216.183 Start Time: Fri, 20 Aug 2021 19:20:02 +0200 Labels: deployment-timestamp=unix-1629479963 pod-template-hash=56ff574674 source=kuberhealthy Annotations: k8s.v1.cni.cncf.io/network-status: [{ "name": "", "interface": "eth0", "ips": [ "10.200.6.98" ],...

See above - second section. That won't be output due to the status.

Nothing too interesting, maybe this? ``` level=info msg="Could not delete service: deployment-svc" --   | September 3rd 2021, 17:15:45.829 | time="2021-09-03T15:15:45Z" level=info msg="Found an old deployment belonging to this check: deployment-deployment"  ...