# Consul Clients Outside of Kubernetes

**URL:** <https://discuss.hashicorp.com/t/consul-clients-outside-of-kubernetes/29696>\
**Category:** Consul\
**Tags:** k8s\
**Created:** [September 20, 2021, 4:29pm UTC](https://discuss.hashicorp.com/t/consul-clients-outside-of-kubernetes/29696 "2021-09-20T16:29:50Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![mbaroody](https://sea2.discourse-cdn.com/hashicorp/user_avatar/discuss.hashicorp.com/mbaroody/32/22454_2.png) [@mbaroody](https://discuss.hashicorp.com/u/mbaroody)\
**Post date:** [September 20, 2021, 4:29pm UTC](https://discuss.hashicorp.com/t/consul-clients-outside-of-kubernetes/29696/1 "2021-09-20T16:29:50Z")

</div>

I was following this guide: [Consul Clients Outside of Kubernetes - Kubernetes | Consul by HashiCorp](https://www.consul.io/docs/k8s/installation/deployment-configurations/clients-outside-kubernetes#auto-join-via-host-ports) until I realized I cannot access EKS nodes by their internal IPs. I can, however, access the EKS nodes by their external IPs when I am behind my company’s VPN. Is there any support for auto-join via host ports using external host IPs?