Closed cweibel closed 4 years ago
Right now kubelet cannot pull images back from KubeCF blobstore since the service does not listen on loopback.
Adding "127.0.0.1/8" to the array of nodePortAddress in the kube-proxy here fixes this issue.
For example the following manual change results in a usable binding:
nodePortAddresses: ["10.128.57.192/28", "127.0.0.1/8"]
After making the change manually to the configmap and recreating the kube-proxy pods apps can successfully stage in KubeCF.
If you add 127.0.0.1/8 (or the more restricted 127.0.0.1/32) to the network.nodes list on the control job I think the the configMap will do what you want.
127.0.0.1/8
127.0.0.1/32
network.nodes
control
I believe this is fixed.
Right now kubelet cannot pull images back from KubeCF blobstore since the service does not listen on loopback.
Adding "127.0.0.1/8" to the array of nodePortAddress in the kube-proxy here fixes this issue.
For example the following manual change results in a usable binding:
After making the change manually to the configmap and recreating the kube-proxy pods apps can successfully stage in KubeCF.