# Using existing nginx controller in GKE

**URL:** <https://forums.suse.com/t/using-existing-nginx-controller-in-gke/37238>\
**Category:** SUSE Rancher Prime\
**Created:** [March 11, 2022, 12:37pm UTC](https://forums.suse.com/t/using-existing-nginx-controller-in-gke/37238 "2022-03-11T12:37:16Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![pulkit-servian](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/pulkit-servian/32/8728_2.png) [@pulkit-servian](https://forums.suse.com/u/pulkit-servian)\
**Post date:** [March 11, 2022, 12:37pm UTC](https://forums.suse.com/t/using-existing-nginx-controller-in-gke/37238/1 "2022-03-11T12:37:16Z")

</div>

I am trying to install Rancher in a private GKE cluster which has an nginx running. How can I point rancher configuration ingress using helm to that nginx controller and not create a new internal load balancert. By default it tries to create an External Load Balancer.