# Bare metal edge proxy with Kong and Kuma

**URL:** <https://discuss.konghq.com/t/bare-metal-edge-proxy-with-kong-and-kuma/7728>\
**Category:** Questions\
**Tags:** service-mesh\
**Created:** [January 12, 2021, 9:34pm UTC](https://discuss.konghq.com/t/bare-metal-edge-proxy-with-kong-and-kuma/7728 "2021-01-12T21:34:51Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![derchris](https://yyz2.discourse-cdn.com/flex036/user_avatar/discuss.konghq.com/derchris/32/2485_2.png) [@derchris](https://discuss.konghq.com/u/derchris)\
**Post date:** [January 12, 2021, 9:34pm UTC](https://discuss.konghq.com/t/bare-metal-edge-proxy-with-kong-and-kuma/7728/1 "2021-01-12T21:34:51Z")

</div>

Dear all,

We have some VPS at different datacenters running Kuma global CP on microk8s - works ✅

AWS & DO K8s clusters connected as remote ✅

The missing piece is the API gateway / ingress. All the VPS don‘t have cloud LoadBalancers and we use simple DNS round-robin to load balance them. They should now route [example.com](http://example.com) to we each cloud / datacenter that has a healthy example\_svc.

All the docs for running Kong with Kuma assume LoadBalancers so I‘m a bit lost here.  
Should I run Kong in hybrid mode on the microk8s and their host VMs to „bridge“ to the host network?

Willing to pay for help!