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] Allow naming of Machine sets #867

Open
steverfrancis opened this issue Jan 22, 2025 · 2 comments
Open

[feature] Allow naming of Machine sets #867

steverfrancis opened this issue Jan 22, 2025 · 2 comments
Labels
UI wireframes required The issue requires some UI wireframes before we can take it into work

Comments

@steverfrancis
Copy link
Contributor

Problem Description

You can create a new worker machine set - but you are given no choice as to the name (at least in the UI) and are forced to accept a name like 'workers-4a7f5e' instead of 'workers-GPU' or something....

Solution

Allow the user to specify the name on creation, and optionally rename later.

Alternative Solutions

No response

Notes

No response

@utkuozdemir
Copy link
Member

Currently our resource names are also the IDs.

So one idea about naming resources (cluster, worker set etc.) is to go AWS way: human-readable names are just tags on the resources. We could do the same via annotations. That way we decouple the ID and the user-preferred name.

@Unix4ever
Copy link
Member

You can name them in the cluster templates. Just not in the UI.

@Unix4ever Unix4ever added the UI wireframes required The issue requires some UI wireframes before we can take it into work label Jan 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
UI wireframes required The issue requires some UI wireframes before we can take it into work
Projects
None yet
Development

No branches or pull requests

3 participants