Omer Ozery
Omer Ozery
it seems that in k8s v1.20.2 (probably even before, i didn't check) the 0.0.0.0 workaround is no longer working, since the default insecure address is already 0.0.0.0 (both for the...
i wrote the comment above **after** i tried it myself.. i was using the "bind-address" workaround on kubeadm deployed clusters v1.18.2, because like you said it was needed and everything...
@ksa-real @weibeld. the documents and your comments above (which are basically documents references) do not reflect what is actually happening, for kubeadm v1.20.2 deployed clusters, repeating it won't make it...