running minikube with --bootstrapper=kubeadm uses minikube as the hard-coded node name

[olgashtivelman]

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

Please provide the following details:

Environment:

Minikube version (use minikube version): v0.25.2

• OS (e.g. from /etc/os-release): Red Hat Enterprise Linux Server 7.4 (Maipo)
• VM Driver (e.g. cat ~/.minikube/machines/minikube/config.json | grep DriverName): "DriverName": "none"
• ISO version (e.g. cat ~/.minikube/machines/minikube/config.json | grep -i ISO or minikube ssh cat /etc/VERSION): none
• Install tools:
• Others:
  The above can be generated in one go with the following commands (can be copied and pasted directly into your terminal):

minikube version
echo "";
echo "OS:";
cat /etc/os-release
echo "";
echo "VM driver": 
grep DriverName ~/.minikube/machines/minikube/config.json
echo "";
echo "ISO version";
grep -i ISO ~/.minikube/machines/minikube/config.json

What happened:
I started minikube in the following way:
minikube start --vm-driver=none --bootstrapper=kubeadm
I want to use kubeadm bootstrapper. BUT I also want to change the name of node to be the same as the machine name (and not fixed to "minikube" ). when I did the above I got a node with the name "minkube" which i did not expect. and I did not manage to find a way to change the name of the node that will work.

What you expected to happen:
node name will be the same as machine name (the way it is if I use localkube). or at least have a way to change the name to what I want.

How to reproduce it (as minimally and precisely as possible):
minikube start --vm-driver=none --bootstrapper=kubeadm
kubectl get nodes -> see that the node name is minikube even though the machine name is different.

Output of minikube logs (if applicable):

Anything else do we need to know:

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