-
Notifications
You must be signed in to change notification settings - Fork 103
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
Redesign Create Cluster Dialog #208
Comments
Thank you @grolu. It will be hard to improve the cluster creation dialog, because people are generally very satisfied with it and we get extremely good feedback. Still, you mention valid points. I guess, I am basically saying, it will be tough to improve in comparison to what we already have. ;-) Solutions for #207/#127 would indeed be nice. As an idea, while you speak about defaults, maybe different "cluster templates" could make sense, too. |
I like the dialog as well. One big improvement could be to restore the last settings for a new cluster creation. I don'T like a wizard. The very first draft was a wizard and the feedback was not so good. |
We will take all comments into consideration. There is no final concept yet and we certainly do not want to make cluster creation more complicated for our users. However, we expect that we can ask our users to think twice before creating a cluster, considering costs, expected workload, etc. (which is, by the way, not an every day task - if so, this should be automated...) |
The Create Cluster Dialog needs a complete overhaul to improve usability. More options have been added to the different tabs of the dialog and the usage is not straight forward anymore (e.g. changing infrastructure on tab#1 reverts options on tab#2 etc.). In addition, we need to integrate more features, e.g. a shoot yaml editor as last step before creation. Therefore we need to completely redesign the create cluster dialog:
Current planned activities:
Maybe this issue (together with #207) also helps solving #127 (reduce costs)
The text was updated successfully, but these errors were encountered: