DevFW-CICD/ingress-nginx-helm
14
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Update echoserver image version in examples

Browse source
This commit is contained in:
Manuel de Brito Fontes 2017-05-28 17:16:13 -04:00
parent f00823fd83
commit b84fc350ee
6 changed files with 95 additions and 7 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

20
controllers/gce/examples/health_checks/health_check_app.yaml
View file

@ -11,7 +11,7 @@ spec:
spec:
containers:
- name: echoheaders
image: gcr.io/google_containers/echoserver:1.4
image: gcr.io/google_containers/echoserver:1.5
ports:
- containerPort: 8080
readinessProbe:
@ -22,6 +22,24 @@ spec:
timeoutSeconds: 1
successThreshold: 1
failureThreshold: 10
env:
- name: NODE_NAME
valueFrom:
fieldRef:
fieldPath: spec.nodeName
- name: POD_NAME
valueFrom:
fieldRef:
fieldPath: metadata.name
- name: POD_NAMESPACE
valueFrom:
fieldRef:
fieldPath: metadata.namespace
- name: POD_IP
valueFrom:
fieldRef:
fieldPath: status.podIP
---
apiVersion: v1
kind: Service

20
controllers/gce/ingress-app.yaml
View file

@ -49,9 +49,27 @@ spec:
spec:
containers:
- name: echoheaders
image: gcr.io/google_containers/echoserver:1.4
image: gcr.io/google_containers/echoserver:1.5
ports:
- containerPort: 8080
env:
- name: NODE_NAME
valueFrom:
fieldRef:
fieldPath: spec.nodeName
- name: POD_NAME
valueFrom:
fieldRef:
fieldPath: metadata.name
- name: POD_NAMESPACE
valueFrom:
fieldRef:
fieldPath: metadata.namespace
- name: POD_IP
valueFrom:
fieldRef:
fieldPath: status.podIP
---
# This is the Ingress resource that creates a HTTP Loadbalancer configured
# according to the Ingress rules.

2
controllers/nginx/README.md
View file

@ -69,7 +69,7 @@ $ kubectl create -f examples/default/rc-default.yaml
First we need to deploy some application to publish. To keep this simple we will use the [echoheaders app](https://github.com/kubernetes/contrib/blob/master/ingress/echoheaders/echo-app.yaml) that just returns information about the http request as output
```
kubectl run echoheaders --image=gcr.io/google_containers/echoserver:1.4 --replicas=1 --port=8080
kubectl run echoheaders --image=gcr.io/google_containers/echoserver:1.5 --replicas=1 --port=8080
```
Now we expose the same application in two different services (so we can create different Ingress rules)

20
examples/health-checks/gce/health_check_app.yaml
View file

@ -11,7 +11,7 @@ spec:
spec:
containers:
- name: echoheaders
image: gcr.io/google_containers/echoserver:1.4
image: gcr.io/google_containers/echoserver:1.5
ports:
- containerPort: 8080
readinessProbe:
@ -22,6 +22,24 @@ spec:
timeoutSeconds: 1
successThreshold: 1
failureThreshold: 10
env:
- name: NODE_NAME
valueFrom:
fieldRef:
fieldPath: spec.nodeName
- name: POD_NAME
valueFrom:
fieldRef:
fieldPath: metadata.name
- name: POD_NAMESPACE
valueFrom:
fieldRef:
fieldPath: metadata.namespace
- name: POD_IP
valueFrom:
fieldRef:
fieldPath: status.podIP
---
apiVersion: v1
kind: Service

20
examples/http-svc.yaml
View file

@ -29,7 +29,23 @@ spec:
spec:
containers:
- name: http-svc
image: gcr.io/google_containers/echoserver:1.3
image: gcr.io/google_containers/echoserver:1.5
ports:
- containerPort: 8080
env:
- name: NODE_NAME
valueFrom:
fieldRef:
fieldPath: spec.nodeName
- name: POD_NAME
valueFrom:
fieldRef:
fieldPath: metadata.name
- name: POD_NAMESPACE
valueFrom:
fieldRef:
fieldPath: metadata.namespace
- name: POD_IP
valueFrom:
fieldRef:
fieldPath: status.podIP

20
examples/multi-tls/nginx/multi-tls.yaml
View file

@ -58,9 +58,27 @@ spec:
spec:
containers:
- name: echoheaders
image: gcr.io/google_containers/echoserver:1.4
image: gcr.io/google_containers/echoserver:1.5
ports:
- containerPort: 8080
env:
- name: NODE_NAME
valueFrom:
fieldRef:
fieldPath: spec.nodeName
- name: POD_NAME
valueFrom:
fieldRef:
fieldPath: metadata.name
- name: POD_NAMESPACE
valueFrom:
fieldRef:
fieldPath: metadata.namespace
- name: POD_IP
valueFrom:
fieldRef:
fieldPath: status.podIP
---
apiVersion: extensions/v1beta1
kind: Ingress