<p>As we know, kubernetes supports 2 primary modes of finding a Service - environment variables and DNS, could we disable the first way and only choose the DNS way?</p>

<p>As shown in this <a href="https://github.com/kubernetes/kubernetes/pull/68754" rel="noreferrer">PR</a>, this feature will land with Kubernetes v1.13. From the PR (as Docs are not available yet) I expect it to be the field <code>enableServiceLinks</code> in the pod spec with true as default.</p>
<p>Edit: It has been a while and the PR finally landed. The <code>enableServiceLinks</code> was added as an optional Boolean to the <a href="https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.20/#podspec-v1-core" rel="noreferrer">Kubernetes PodSpec</a>.</p>
<p>For the record: <a href="https://kubernetes.io/docs/concepts/services-networking/connect-applications-service/#dns" rel="noreferrer">using DNS</a> to discover service endpoints is the recommended approach. The <code>docker link</code> behavior, from where the environment variables originate, has long been <a href="https://docs.docker.com/compose/compose-file/compose-file-v1/#link-environment-variables" rel="noreferrer">deprecated</a>.</p>
