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

Updated docs for cluster metadata map #22

Merged
merged 5 commits into from
Jun 10, 2019
Merged

Updated docs for cluster metadata map #22

merged 5 commits into from
Jun 10, 2019

Conversation

jpapejr
Copy link
Contributor

@jpapejr jpapejr commented May 28, 2019

Folks will probably want to use more human-readable values in the dashboard for clusters (a customizable name vs a generated ID). The functionality is already there (because Razee is awesome) but the docs just don't mention it. This PR fixes that.

@jpapejr jpapejr changed the title Updated docs for cluster metadate map Updated docs for cluster metadata map May 28, 2019
@alewitt2
Copy link
Member

can you make this step 5 of this section. And label it optional. something like 5. Optional:

@jpapejr
Copy link
Contributor Author

jpapejr commented May 30, 2019

Will do.

@jpapejr
Copy link
Contributor Author

jpapejr commented May 31, 2019

README.md Outdated
namespace: default
````

After the ConfigMap is picked up (within a few moments), Razee will diplay this cluster on the dashboard using `razee-1` instead of the long ID value seen before. Note that it may take up to 2 minutes before the change can be seen in the dashboard.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

typo: diplay

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

and it should only take up to 1 minute before change can be seen

@alewitt2
Copy link
Member

thanks

@alewitt2 alewitt2 merged commit 4f66dcc into razee-io:master Jun 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants