# Isolate Dremio Services in Kubernetes **URL:** https://community.dremio.com/t/isolate-dremio-services-in-kubernetes/9828 **Category:** Uncategorized **Created:** [October 18, 2022, 5:52am UTC](https://community.dremio.com/t/isolate-dremio-services-in-kubernetes/9828 "2022-10-18T05:52:40Z") **Posts on this page:** 1 **Showing post:** 3
### Author: ![ramprasd89](https://avatars.discourse-cdn.com/v4/letter/r/0ea827/32.png) [@ramprasd89](https://community.dremio.com/u/ramprasd89) #### Post date: [October 19, 2022, 6:52am UTC](https://community.dremio.com/t/isolate-dremio-services-in-kubernetes/9828/3 "2022-10-19T06:52:42Z")
Hi @lenoyjacob - Thanks for the quick response! In the template here - would you recommend us to have 3 different services by only altering the spec.ports.port, with each service having only their respective port/targetport/name parameters? As requested, please find more details on the use case below: We have deployed Dremio on an AKS cluster and have exposed the UI behind an Azure App Gateway, with WAF features enabled. The UI(exposed as a service - dremio-client - on port 9047) is accessible behind the App Gateway without any issues, however when we tried to establish ArrowFlight connection(which is again exposed on same service - dremio-client - on port 32010), there were issues with the App GW not being able to realize the HTTP2 protocol, arrowflight uses. As a result, we were forced to split the “dremio-client” into 2 - one for the UI(port 9047 and routed through AppGW) and the other for arrowflight connection(port 32010 and routed through layer 4 LoadBalancer). Hence the need for splitting the services. More details could be found in the ticket here - [Accessing Dremio running behind App Gateway from Superset](https://community.dremio.com/t/accessing-dremio-running-behind-app-gateway-from-superset/9745) --- _[View the full topic](https://community.dremio.com/t/isolate-dremio-services-in-kubernetes/9828)._