From cc64c39bac8af9655fe12cd3cbe81ce62ab8b58a Mon Sep 17 00:00:00 2001 From: Eduardo Roldan Date: Tue, 6 Aug 2019 04:49:55 -0300 Subject: [PATCH] Document the enableServiceLinks flag (#15611) * Document the enableServiceLinks flag There are many cases of service discovery environment variables clashing with env vars expected by programs, causing hard to debug problems. The enableServiceLinks flag added in 1.13 should be mentioned here and not only on the API reference. * Update connect-applications-service.md * Update content/en/docs/concepts/services-networking/connect-applications-service.md Co-Authored-By: Qiming * rephrased the action to use active voice style --- .../services-networking/connect-applications-service.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/content/en/docs/concepts/services-networking/connect-applications-service.md b/content/en/docs/concepts/services-networking/connect-applications-service.md index 073e83abdd..96d7cc195b 100644 --- a/content/en/docs/concepts/services-networking/connect-applications-service.md +++ b/content/en/docs/concepts/services-networking/connect-applications-service.md @@ -134,6 +134,12 @@ about the [service proxy](/docs/concepts/services-networking/service/#virtual-ip Kubernetes supports 2 primary modes of finding a Service - environment variables and DNS. The former works out of the box while the latter requires the [CoreDNS cluster addon](http://releases.k8s.io/{{< param "githubbranch" >}}/cluster/addons/dns/coredns). +{{< note >}} +If the service environment variables are not desired (because possible clashing with expected program ones, +too many variables to process, only using DNS, etc) you can disable this mode by setting the `enableServiceLinks` +flag to `false` on the [pod spec](/docs/reference/generated/kubernetes-api/{{< param "version" >}}/#pod-v1-core). +{{< /note >}} + ### Environment Variables