4

I keep reading documentation that gives parameters for kube-proxy, but does not explain how where these parameters are supposed to be used. I create my cluster using az aks create with the azure-cli program, then I get credentials and use kubectl. So far everything I've done has involved yaml for services and deployments and such, but I can't figure out where all this kube-proxy stuff fits into all of this.

I've googled for days. I've opened question issues on github with AKS. I've asked on the kubernetes slack channel, but nobody has responded.

Novaterata
  • 4,356
  • 3
  • 29
  • 51

1 Answers1

8

The kube-proxy on all your Kubernetes nodes runs as a Kubernetes DaemonSet and its configuration is stored on a Kubernetes ConfigMap. To make any changes or add/remove options you will have to edit the kube-proxy DaemonSet or ConfigMap on the kube-system namespace.

$ kubectl -n kube-system edit daemonset kube-proxy

or 

$ kubectl -n kube-system edit configmap kube-proxy

For a reference on the kube-proxy command line options you can refer to here.

Rico
  • 58,485
  • 12
  • 111
  • 141
  • OMG Thanks! I will test it soon. Do I need to do anything to make it take effect quicker? Also, do you know how to restart the kube-apiserver on an AKS cluster? – Novaterata Oct 12 '18 at 17:39
  • Not sure. Most of the cloud providers don't give you access to the master. you could try `kube patch` the api server pod. – Rico Oct 12 '18 at 17:41
  • oh well. I keep getting "Insufficient memory" for pods when there is clearly sufficient memory and that was a workaround, but I'm having to delete the whole cluster and create it again. It's very frustrating trying to determine the correct resource limits when it behaves differently each time i edit the deployment – Novaterata Oct 12 '18 at 17:44
  • The daemonset existed and I believe it's working. The configmap did not exist though – Novaterata Oct 12 '18 at 18:17
  • Maybe the AKS config is unique and they don't use a ConfigMap – Rico Oct 12 '18 at 18:22