kube-addon-manager-ubuntu not starting

[ctaggart]

The kube-addon-manager-ubuntu is not starting. I'm running Ubuntu 18.04 LTS and I've tried both minikube v0.28.0 and v0.27.0. I'm using localkube because your can't configure proxy yet on kubeadm #2259 .

Here is the config I'm using.

sudo minikube start \
  --bootstrapper=localkube \
  --vm-driver=none \
  --network-plugin=cni \
  --host-only-cidr=172.17.17.1/24 \
  --extra-config=kubelet.network-plugin=cni \
  --extra-config=kubelet.PodCIDR=192.168.0.0/16 \
  --extra-config=proxy.ClusterCIDR=192.168.0.0/16 \
  --extra-config=controller-manager.ClusterCIDR=192.168.0.0/16

cameron@ubuntu:~/calico$ kubectl get --all-namespaces pod
NAMESPACE     NAME                        READY     STATUS             RESTARTS   AGE
kube-system   kube-addon-manager-ubuntu   0/1       CrashLoopBackOff   1          29s
cameron@ubuntu:~/calico$ kubectl -n kube-system log kube-addon-manager-ubuntu
failed to open log file "/var/log/pods/3afaf06535cc3b85be93c31632b765da/kube-addon-manager/3.log": open /var/log/pods/3afaf06535cc3b85be93c31632b765da/kube-addon-manager/3.log: no such file or directory

I'm not sure if it is related to:

• minikube --none driver not starting addons in all cases minikube --none driver not starting addons in all cases #1771
• Most of the pods of kube-system went to CrashLoopBackOff when started minikube with --vm-driver=none Most of the pods of kube-system went to CrashLoopBackOff when started minikube with --vm-driver=none #2496

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.