Closed unixfox closed 4 years ago
I thought it was an isolated bug with Kubernetes 1.18 but in fact it's coming back in Kubernetes 1.16.
In fact the code was relying on status from an older version of Kubernetes and now it's working with Kubernetes >1.16.
I thought it was an isolated bug with Kubernetes 1.18 but in fact it's coming back in Kubernetes 1.16.