Do not include /etc/cni/net.d/k8s.conf in rootfs by default

[brb]

Is this a BUG REPORT or FEATURE REQUEST? (choose one):

FEATURE REQUEST

Currently, minikube ships with /etc/cni/net.d/k8s.conf in rootfs.

When using minikube with other CNI network providers, e.g. Weave Net, kubelet might use the config when starting pods till the provider has provisioned its CNI config, which results in some pods being attached to mybridge instead of the weave bridge. Some manual steps are required to prevent from this happening: weaveworks/weave#3124 (comment).

Instead of shipping k8s.conf inside rootfs, I suggest to add a param to minikube start which would trigger provisioning of k8s.conf.

If this makes sense to you, I'm happy to open a PR.

[dlorenc]

This sgtm. Let me know when you send the PR!

[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.