whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Clean up docker references from Service documentations

Browse Source 
1. Remove examples contrasting k8s networking with Docker networking
from concept document explaining connecting applications using services
2. Remove reference to dockerlinks in favor of English description
of the env vars autocreated for every Service.
This commit is contained in:
Yashodhan Mohan Bhatnagar
2022-01-14 02:39:33 +05:30
parent 66081efd04
commit a18a34c482
2 changed files with 5 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/concepts/services-networking/service.md
+2 -3
View File
@@ -450,9 +450,8 @@ variables and DNS.
### Environment variables
When a Pod is run on a Node, the kubelet adds a set of environment variables
for each active Service. It supports both [Docker links
compatible](https://docs.docker.com/userguide/dockerlinks/) variables (see [makeLinkVariables](https://github.com/kubernetes/kubernetes/blob/dd2d12f6dc0e654c15d5db57a5f9f6ba61192726/pkg/kubelet/envvars/envvars.go#L72))
and simpler `{SVCNAME}_SERVICE_HOST` and `{SVCNAME}_SERVICE_PORT` variables,
for each active Service. It supports both granular variables like `{SVCNAME}_PORT_{SVCPORT}_PROTO` and more (see [makeLinkVariables](https://github.com/kubernetes/kubernetes/blob/dd2d12f6dc0e654c15d5db57a5f9f6ba61192726/pkg/kubelet/envvars/envvars.go#L72))
as well as simpler `{SVCNAME}_SERVICE_HOST` and `{SVCNAME}_SERVICE_PORT` variables,
where the Service name is upper-cased and dashes are converted to underscores.
For example, the Service `redis-master` which exposes TCP port 6379 and has been