Error starting the kube-proxy service

[anton-johansson]

According to the kube-proxy.service.j2 we're running kube-proxy with this command:

/usr/local/bin/kube-proxy --config=/etc/kubernetes/config/kube-proxy.yml

When I do that I get the following error:

F1214 16:56:03.067953   14535 server.go:361] invalid configuration: no configuration has been provided

I googled around a bit, and found this, which shows a different command. If I run this, my kube-proxy runs:

/usr/local/bin/kube-proxy --master=https://{{ cluster_hostname }}:{{ cluster_port }} --kubeconfig=/etc/kubernetes/config/kube-proxy.kubeconfig --v=2

The above command makes kube-proxy.yml a bit useless. Am I missing something? It's worth noting that I haven't gotten my cluster fully set up yet, so I haven't verified that everything works with the above command. :)

EDIT: Probably same issue as kelseyhightower/kubernetes-the-hard-way/issues/391

[amimof]

@anton-johansson i can't seem to reproduce this. Do you have failed tasks after running install.yml? What OS are you running on?

[anton-johansson]

I'm using Ubuntu Server 18.04 and the same versions of all packages (kube-proxy, kube-apiserver, etc) as this repository has. I haven't used your install.yml directly, because I'm trying to understand all the pieces, so I might have messed something up a long the way.

There are no failed tasks when running install.yml, the kube-proxy just fails to start.

I'll dig a bit deeper and see if I can get the cluster up and running first.

[amimof]

@anton-johansson So I think i figured out what is going on. Seems that the variable cluster_config_path is never set when you run kube-proxy role since the variable is set in role certificates. This means that the roles have dependencies between them and of course we don't want that.

[anton-johansson]

Nice catch! However, I think my issue is unrelated. I tested using the master branch of this repository (with the addition of #8) instead of my own custom one and it worked flawlessly.

I'll close this issue for now, but I'll comment here again when once I find what my problem was. :)