Remove colon from end of doc heading.
This commit is contained in:
@@ -97,7 +97,7 @@ You should now be able to curl the nginx Service on `10.0.208.159:80` from any n
|
||||
|
||||
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 [kube-dns cluster addon](../../cluster/addons/dns/README.md).
|
||||
|
||||
### Environment Variables:
|
||||
### Environment Variables
|
||||
When a Pod is run on a Node, the kubelet adds a set of environment variables for each active Service. This introduces an ordering problem. To see why, inspect the environment of your running nginx pods:
|
||||
```shell
|
||||
$ kubectl exec my-nginx-6isf4 -- printenv | grep SERVICE
|
||||
@@ -119,7 +119,7 @@ KUBERNETES_SERVICE_HOST=10.0.0.1
|
||||
NGINXSVC_SERVICE_PORT=80
|
||||
```
|
||||
|
||||
### DNS:
|
||||
### DNS
|
||||
Kubernetes offers a DNS cluster addon Service that uses skydns to automatically assign dns names to other Services. You can check if it’s running on your cluster:
|
||||
```shell
|
||||
$ kubectl get services kube-dns --namespace=kube-system
|
||||
|
Reference in New Issue
Block a user