Hi, I am running HBase clusters on Kubernetes and have been looking at how to patch the code (version 2.6.1) so that the links on the master and regionserver UIs are resolvable. My approach involves extending the ServerName struct to include two new fields (e.g. externalHostname and externalPort), which are filled with e.g. the node IP and externally resolvable port, prepared by my operator and stored in custom config settings. This means that I can use this information whenever a ServerName object is retrieved for the active master, and I have patched the relevant jsp pages to use this information instead of the internal name. However, it is a) fairly invasive, and b) not a complete solution, as at some points in the code (e.g. the regionServers collection in RegionServerTracker) only the hostname of the struct is used and not the whole struct (so additional fields are not available). I'm aware that things will change as of 4.0.0 anyway, when some of the meta data will be stored in an HBase table instead of ZooKeeper. Has anyone else started thinking about or working on this? Is there a work-in-progress that we could support upstream?
Andrew
