# GKE Internal Load Balancer

**URL:** <https://community.hivemq.com/t/gke-internal-load-balancer/1450>\
**Category:** HiveMQ Community Edition\
**Created:** [September 20, 2022, 11:45pm UTC](https://community.hivemq.com/t/gke-internal-load-balancer/1450 "2022-09-20T23:45:23Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![tfly12](https://avatars.discourse-cdn.com/v4/letter/t/da6949/32.png) [@tfly12](https://community.hivemq.com/u/tfly12)\
**Post date:** [September 20, 2022, 11:45pm UTC](https://community.hivemq.com/t/gke-internal-load-balancer/1450/1 "2022-09-20T23:45:23Z")

</div>

Hello! I am new to HiveMQ and I am trying to create a Kubernetes cluster in GKE to run HiveMQ. I was able to follow [this guide](https://www.hivemq.com/docs/operator/4.8/kubernetes-operator/operator-intro.html#install) to install using helm. However, our organization does not allow external load balancers to be configured on Kubernetes services.

I was hoping someone else has either run into this or can help me reconfigure the load balancer to be an Internal Load Balancer instead of an external load balancer using the Kubernetes operator provided by HiveMQ. Thanks!

---

<div class="post-metadata">

**Author:** ![Daria\_H](https://avatars.discourse-cdn.com/v4/letter/d/dfb087/32.png) [@Daria\_H](https://community.hivemq.com/u/Daria_H)\
**Post date:** [October 6, 2022, 9:05am UTC](https://community.hivemq.com/t/gke-internal-load-balancer/1450/2 "2022-10-06T09:05:02Z")

</div>

Hi @tfly12 ,

It is great to see your interest in MQTT and HiveMQ, welcome to the community. Thank you for your question. Could you please help me understand, what is the difference (according to your organization) between internal and external load balancer?

- How is your service getting configured when you are following the guide? Can you share the service YAML?
- How would your ogranization expect it to be configured?
- Can you share an internal load balancer example that is allowed in your organization?

Thanks,  
Dasha from HiveMQ team
