Matt McNaughton
0a56b9db51
Going through the guestbook tutorial for the first time, the deployment configuration mentioned that whether my configuration included a DNS service would dictate which env value I used for the `GET_HOSTS_FROM` variable. According to https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/, k8s includes DNS by default starting with v1.3. Add this additional info to help the user better understand when DNS may/may not be enabled.
34 lines
999 B
YAML
34 lines
999 B
YAML
apiVersion: extensions/v1beta1
|
|
kind: Deployment
|
|
metadata:
|
|
name: redis-slave
|
|
spec:
|
|
replicas: 2
|
|
template:
|
|
metadata:
|
|
labels:
|
|
app: redis
|
|
role: slave
|
|
tier: backend
|
|
spec:
|
|
containers:
|
|
- name: slave
|
|
image: gcr.io/google_samples/gb-redisslave:v1
|
|
resources:
|
|
requests:
|
|
cpu: 100m
|
|
memory: 100Mi
|
|
env:
|
|
- name: GET_HOSTS_FROM
|
|
value: dns
|
|
# Using `GET_HOSTS_FROM=dns` requires your cluster to
|
|
# provide a dns service. As of Kubernetes 1.3, DNS is a built-in
|
|
# service launched automatically. However, if the cluster you are using
|
|
# does not have a built-in DNS service, you can instead
|
|
# instead access an environment variable to find the master
|
|
# service's host. To do so, comment out the 'value: dns' line above, and
|
|
# uncomment the line below:
|
|
# value: env
|
|
ports:
|
|
- containerPort: 6379
|