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
cli,ui: make CRDB recognize the CC cluster name in configuration and display it in DB Console and other places #44494
Comments
Caveat: the "cluster name" introduced in 19.2 is non-customizable. If users want a customizable strings, that would be a different feature. |
Discussed this with the CockroachCloud team: in CC the (logical) cluster name is prominently displayed in the URL bar of the browser, because CC uses the cluster name in the hostname of the admin UI. From a UX perspective this is already a great step forward to achieve the goal (distinguishing diffrent clusters in the browser). I still think we should display the value of |
Bumping this for 20.2, we have heard several points of feedback that users would prefer to see the cluster name in the Admin UI instead of cluster ID. cc @Annebirzin |
Note that we probably need a new concept (customizable cluster label) separate from the "cluster name" functionality which cannot easily be customized after the cluster is started. |
This came up again today from @smcvey . (slack thread) |
In CC it is customary when raising a support case to share the CC "cluster name" ("friendly ID") with the team. However, when in front of DB console that cluster name is not displayed anywhere.
It would be useful to make CRDB recognize an optional and configurable "cluster name" for display purposes and this would be reported:
cockroach node
,cockroach init
Note: this feature is different from the (internal) "cluster name" used by the RPC protocol authentication, which is immutable and should remain relatively secret. Perhaps the internal value could be renamed to "cluster key" for clarity.
cc @awoods187 who was asking about it
Jira issue: CRDB-5223
The text was updated successfully, but these errors were encountered: