Can cattle-cluster-agent use private ip instead of public https?


I’m using rancher with a docker-compose setup on a single instance to monitor existing gke clusters.

I wanted to know if it was possible that the cattle-cluster-agent use the private ip of the rancher virtual machine instead of the public facing https access. I didn’t find anything like that in the documentation.

I want that because I want to whitelist who can access the the admin interface (another solution for me would be to add a cloud nat provided by gcp and whitelist this ip…

Thank you