# Do DNS discovery and consul to k8s service sync still enforce mTLS?

**URL:** <https://discuss.hashicorp.com/t/do-dns-discovery-and-consul-to-k8s-service-sync-still-enforce-mtls/13246>\
**Category:** Consul\
**Tags:** dns, connect, k8s-service-sync, service-mesh\
**Created:** [August 23, 2020, 3:49pm UTC](https://discuss.hashicorp.com/t/do-dns-discovery-and-consul-to-k8s-service-sync-still-enforce-mtls/13246 "2020-08-23T15:49:29Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![blake](https://sea2.discourse-cdn.com/hashicorp/user_avatar/discuss.hashicorp.com/blake/32/27620_2.png) [@blake](https://discuss.hashicorp.com/u/blake)\
**Post date:** [August 24, 2020, 4:27pm UTC](https://discuss.hashicorp.com/t/do-dns-discovery-and-consul-to-k8s-service-sync-still-enforce-mtls/13246/2 "2020-08-24T16:27:22Z")

</div>

Hi @agniveshadhikari,

There’s an open feature request to add this functionality.

> <https://github.com/hashicorp/consul/issues/6417>
>
> Feature Description
> Right now Consul Connect makes assumptions about a proxy being deployed as a sidecar and where the application can just...

Related to that, we are also looking to add support for transparent proxying which will allow applications to address services by their configured hostname (e.g., [api.example.com](http://api.example.com)) and have that request automatically re-routed to the sidecar proxy.

> <https://github.com/hashicorp/consul-k8s/issues/23>
>
> In a similar vein to #22, I'd be interested in seeing options to make pods less aware of Consul.
> I've noticed that...

In the interim, you will need to make calls to `localhost` as you have identified.

---

_[View the full topic](https://discuss.hashicorp.com/t/do-dns-discovery-and-consul-to-k8s-service-sync-still-enforce-mtls/13246)._