Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: be able to configure node name on node creation #242

Open
mbelchin opened this issue Feb 19, 2019 · 2 comments
Open

Feature Request: be able to configure node name on node creation #242

mbelchin opened this issue Feb 19, 2019 · 2 comments

Comments

@mbelchin
Copy link

Right now, when you create a new node, CSE picks a random node name, would be great to be able to define the name for the node on creation

@sahithi
Copy link
Collaborator

sahithi commented Feb 19, 2019

Hi,

Can you please state your use-cases on why you want to specify custom names for nodes? FYI, CSE uses strict naming convention to execute some logic internally. Your request is doable but would like to understand your cases better before we evaluate this further.

@mbelchin
Copy link
Author

mbelchin commented Feb 21, 2019

This is our use case:

Usually we use this naming convention master-XXX for masters or node-XXX for worker nodes.

The XXX is a number, i.e.: master-001, master-002, node-001, node-002, ... node-110, etc.

We make that XXX number to be the last part of our internal IPs, .i.e:
master node -> IP: 10.0.0.1 -> master-001
master node -> IP: 10.0.0.23 -> master-023
worker node -> IP: 10.0.0.172 -> node-172
worker node -> IP: 10.0.0.21 -> node-021

This way we can easily, at a glance, identify the node but also the internal IP for that node and we can really quick SSH into that node. We have some ssh custom config which allows us to do something like:
ssh [email protected]

Once you're inside the node through SSH, you always see the machine name as node-021 so you always know where you are. Simpler tan node-xr7j

Furthermore, we use external tool to monitorize our clusters and those tools send alerts. On that system we have also configured the names of the machines following same approach, node-XXX, master-XXX so it's quite handy whenever you receive the alert because you know how to connect to the node and fix the issue quickly.

Also when working with kubectl command plus the argument -o wide, you can filter for a specific node, using grep for instance. In this case is also way simpler to remind node-021 than node-x3ts.

So, would be great if at least we could define the random part of the name for new nodes. So your template could continue doing steps based on node-XXXX but the random part it's something configurable by the user.

If you need further clarifications, please feel free to contanct me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants