Update --disable-driver-mounts default to false

[deepdad]

Please remove the standard Shared Folder on VirtualBox and guide users how and when to use it. The shared folder isn't used by the Hello minikube tutorial. It can easily be forgotten while users start deploying apps that generate outgoing traffic. I don't know how hard it is to then start uploading data from the default shared folder, but I think it could involve merely a docker image with elevated user rights.

DisableDriverMounts bool // Only used by virtualbox

[deepdad]

I would also use a no outgoing egress on all namespaces to be turned off as part of hello minikube: you seem to need outgoing traffic for basic execution. I see a lot of traffic run off from images that are parts of tutorials. I don't know what that is about, probably usage monitoring but that's still univited and never mentioned.

[afbjorklund]

It used to be controlled by a flag: minikube start --disable-driver-mounts (#1645 / #1646)

However, for some reason this flag is now missing from v1.3.0 options ?

@medyagh : looks like it was lost from virtualbox, when "grouping": 089bacc

[afbjorklund]

Suggest bringing the flag back for v1.3.1, consider flipping it for a future release perhaps ?

Here is the list of folders that are shared by default, when using VirtualBox (and some others):

https://kubernetes.io/docs/setup/learning-environment/minikube/#mounted-host-folders

[afbjorklund]

Actually it got lost in the merge conflict resolution: 1b83a89 by @tstromberg

Sadly git doesn't show these (merge commits) properly, when doing the pick-axe.

[deepdad]

What pods and stuff have sudo privilege ? After installing minikube with sudo, is running $minikube actually doing $sudo minikube?

[afbjorklund]

After installing minikube with sudo, is running $minikube actually doing $sudo minikube

It might (for the none driver), but normally it will do that in the VM - and not on the host.

However, it will not be for re-running minikube itself but for commands like sudo kubeadm

We warn against running minikube as root (or with sudo), there should be no need for that.

You still need enough administrator privileges to use the hypervisor, but that is another story...

[tstromberg]

Related: #5019

[medyagh]

we will not do this issue, till we have a solution for non-9p mounts

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