Skip to content

Drop "headless" from the service name #415

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.

Sign up for GitHub

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

Jump to bottom
Closed
mkuratczyk opened this issue Oct 27, 2020 · 0 comments · Fixed by #447
Closed

Drop "headless" from the service name #415

mkuratczyk opened this issue Oct 27, 2020 · 0 comments · Fixed by #447
Assignees
@ChunyiLyu
Milestone
GA

Comments

@mkuratczyk
Copy link
Collaborator

We've heard feedback that the word "headless" in the service name is confusing - it's a very technical aspect of the service that leaks into many places, including all names in the Prometheus metrics. It also makes all names quite a bit longer (again, that mostly affects for monitoring). Unless we see a good reason to keep it, we should just drop "headless" from the service name.
@mkuratczyk mkuratczyk added this to the GA milestone Oct 27, 2020
@ChunyiLyu ChunyiLyu self-assigned this Oct 27, 2020
@ChunyiLyu ChunyiLyu mentioned this issue Oct 29, 2020
Closed
@ChunyiLyu ChunyiLyu mentioned this issue Nov 6, 2020
Merged
mkuratczyk added a commit that referenced this issue Nov 23, 2020
@mkuratczyk
Update service name in the binding
142f17d 
We've change the name of the service in #415
@mkuratczyk mkuratczyk mentioned this issue Nov 23, 2020
Merged
mkuratczyk added a commit that referenced this issue Nov 23, 2020
@mkuratczyk
Update service name in the binding (#486)
b2061cc 
We've change the name of the service in #415
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ChunyiLyu ChunyiLyu

Labels
None yet
Projects
None yet
Milestone
GA
Development

Successfully merging a pull request may close this issue.

Rename rabbitmq/cluster-operator
Renaming rabbitmq/cluster-operator
2 participants
@ChunyiLyu @mkuratczyk