# Failed to ensure load balancer for service default/quickstart-es-http

**URL:** https://discuss.elastic.co/t/failed-to-ensure-load-balancer-for-service-default-quickstart-es-http/226078
**Category:** Elastic Cloud on Kubernetes (ECK)
**Created:** [April 1, 2020, 3:30pm UTC](https://discuss.elastic.co/t/failed-to-ensure-load-balancer-for-service-default-quickstart-es-http/226078 "2020-04-01T15:30:24Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![tillias](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tillias/32/64271_2.png) [@tillias](https://discuss.elastic.co/u/tillias)
#### Post date: [April 2, 2020, 6:30am UTC](https://discuss.elastic.co/t/failed-to-ensure-load-balancer-for-service-default-quickstart-es-http/226078/5 "2020-04-02T06:30:24Z")

</div>

Hi Anya,

Sorry that I didn't mentioned it before, we're using Open Telekom Cloud as a cloud provider and managed Kubernetes Cluster there. I agree this is provider specific issue, because in GKE it works fine. Is there any possibility to configure / tune Load Balancer settings like we did with storage class in this topic [Pod has unbound immediate PersistentVolumeClaims](https://discuss.elastic.co/t/pod-has-unbound-immediate-persistentvolumeclaims/223788) ?

---

_[View the full topic](https://discuss.elastic.co/t/failed-to-ensure-load-balancer-for-service-default-quickstart-es-http/226078)._