chore: advertise restserver in rolegroup configmap#708
Merged
Conversation
Member
|
This is not in 25.11, correct? |
Member
Author
No, not in 25.11 Release Note
Adjusted Release Note in #716 (comment) |
This was referenced Nov 17, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Implementation of #669
Adds
hbase.rest.hostnamehbase.rest.porthbase.rest.info.portproperties to the restserver rolegroup configmap.
hbase.rest.hostnameandhbase.rest.info.portare not pre-existinghbase-site.xmlkeys, but were added with a similar naming scheme as master properties.Advertisement of restservers was done to be consistent with master and regionserver advertisement.
Note
(also added to the issue)
Added by @adwk67 The aim here is not to implement full discoverability for role endpoints; that should be done when we tackle that for all operators. We actually reached a point in the original implementation of HBase listener-endpoints where there was a config map (like kafka, hdfs etc.) that listed the endpoints by pod/replica, and at that point we decided against doing that as
So I understand the scope of this ticket to be about bringing the rest-server inline with the other roles, without claiming this to be the final destination.
Definition of Done Checklist
Author
Reviewer
Acceptance
type/deprecationlabel & add to the deprecation scheduletype/experimentallabel & add to the experimental features tracker