Hi! I also proposed another approach in HBASE-29762. It worked fine in my development environment using Istio, or with a NodePort service publication. However we did not reach a consensus on whether this is the right approach. I didn't merge the last PR, but it is now done.
Lars, could you give more details about your approach? It is not clear to me how clients connect to the HBase cluster. I also checked your HBase source code, however I didn't find any code paths which handle the hbase.listener.endpoint configuration setting. Best regards, Balazs On Thu, Feb 19, 2026 at 4:57 PM Lars Francke <[email protected]> wrote: > Hi, > > I realise this is a super late response. I just stumbled across your > question. > We have built a Kubernetes operator for HBase and are using a concept > we call "Listeners" to make the behavior configurable for our users. > So it's either LoadBalancer or ClusterIP or NodePort depending on the > requirements. > > https://docs.stackable.tech/home/stable/listener-operator/listenerclass/#preset-details > > This is working fine for us and our customers. > Happy to talk more if it helps. > > Cheers, > Lars > > On Tue, Jan 6, 2026 at 2:28 AM Kang Minwoo <[email protected]> > wrote: > > > > Hello HBase Community, > > > > We are considering running HBase on Kubernetes and are exploring ways to > allow external access to RegionServers from outside the Kubernetes cluster. > > > > We are concerned that routing large-scale traffic through a load > balancer may cause issues, and using host networking also seems problematic. > > > > If anyone has experience operating HBase on Kubernetes, could you share > how you enabled external access to RegionServers? What approaches or best > practices have you found effective? > > > > Any insights or examples would be greatly appreciated. > > > > Thank you! >
