Skip to content
This repository has been archived by the owner on Apr 22, 2020. It is now read-only.

Change the default names of the nodes after a kubernetes cluster is deployed in vSphere #295

Closed
BaluDontu opened this issue Dec 15, 2016 · 3 comments
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@BaluDontu
Copy link
Contributor

Currently, after a successful deployment of kubernetes cluster in vSphere, the master is named as "master" and the nodes are named as "node1", "node2" and so on.

It is better if we prefix the name of the nodes with kubernetes so that the user can identify this is a kubernetes cluster deployed in the vSphere. So the plan is to modify the default name of the nodes to

"kubernetes-master"
"kubernetes-worker-1"
"kubernetes-worker-2" etc.

@BaluDontu BaluDontu changed the title Change the default names of the nodes in kubernetes cluster in vSphere Change the default names of the nodes after a kubernetes cluster is deployed in vSphere Dec 15, 2016
@vmtocloud
Copy link

Also second this request, ability to be able to set the name prefix in the make config portion would be ideal!

@fejta-bot
Copy link

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.

Prevent issues from auto-closing with an /lifecycle frozen comment.

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

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 2, 2018
@errordeveloper
Copy link
Contributor

/close

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

5 participants