Skip to content

Commit

Permalink
Fix image version
Browse files Browse the repository at this point in the history
  • Loading branch information
aledbf committed Jan 28, 2020
1 parent 0c9ff1a commit f27f5ba
Show file tree
Hide file tree
Showing 4 changed files with 6 additions and 6 deletions.
2 changes: 1 addition & 1 deletion deploy/cloud-generic/kustomization.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ resources:
- service.yaml
images:
- name: quay.io/kubernetes-ingress-controller/nginx-ingress-controller
newTag: master
newTag: 0.28.0
vars:
- fieldref:
fieldPath: metadata.name
Expand Down
2 changes: 1 addition & 1 deletion docs/deploy/upgrade.md
Original file line number Diff line number Diff line change
Expand Up @@ -33,7 +33,7 @@ The easiest way to do this is e.g. (do note you may need to change the name para

```
kubectl set image deployment/nginx-ingress-controller \
nginx-ingress-controller=quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.18.0
nginx-ingress-controller=quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.28.0
```

For interactive editing, use `kubectl edit deployment nginx-ingress-controller`.
Expand Down
6 changes: 3 additions & 3 deletions docs/examples/grpc/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,12 +13,12 @@ nginx controller.
for the ingress).
3. You have the nginx-ingress controller installed in typical fashion (must be
at least
[quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.13.0](https://quay.io/kubernetes-ingress-controller/nginx-ingress-controller)
[quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.28.0](https://quay.io/kubernetes-ingress-controller/nginx-ingress-controller)
for grpc support.
4. You have a backend application running a gRPC server and listening for TCP
traffic. If you prefer, you can use the
[fortune-teller](https://github.com/kubernetes/ingress-nginx/tree/master/images/grpc-fortune-teller)
application provided here as an example.
application provided here as an example.

### Step 1: kubernetes `Deployment`

Expand Down Expand Up @@ -108,7 +108,7 @@ $ grpcurl fortune-teller.stack.build:443 build.stack.fortune.FortuneTeller/Predi
### Notes on using response/request streams

1. If your server does only response streaming and you expect a stream to be open longer than 60 seconds, you will have to change the `grpc_read_timeout` to acommodate for this.
2. If your service does only request streaming and you expect a stream to be open longer than 60 seconds, you have to change the
2. If your service does only request streaming and you expect a stream to be open longer than 60 seconds, you have to change the
`grpc_send_timeout` and the `client_body_timeout`.
3. If you do both response and request streaming with an open stream longer than 60 seconds, you have to change all three timeouts: `grpc_read_timeout`, `grpc_send_timeout` and `client_body_timeout`.

Expand Down
2 changes: 1 addition & 1 deletion docs/examples/static-ip/nginx-ingress-controller.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@ spec:
# hostNetwork: true
terminationGracePeriodSeconds: 60
containers:
- image: quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.18.0
- image: quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.28.0
name: nginx-ingress-controller
readinessProbe:
httpGet:
Expand Down

0 comments on commit f27f5ba

Please sign in to comment.