From 19e9e9d7ed9d016d64ed726bb48513dfedd423a5 Mon Sep 17 00:00:00 2001 From: Manuel Alejandro de Brito Fontes Date: Tue, 28 Jan 2020 08:56:12 -0300 Subject: [PATCH] Fix image version (#4977) --- deploy/cloud-generic/kustomization.yaml | 2 +- docs/deploy/upgrade.md | 2 +- docs/examples/grpc/README.md | 6 +++--- docs/examples/static-ip/nginx-ingress-controller.yaml | 2 +- 4 files changed, 6 insertions(+), 6 deletions(-) diff --git a/deploy/cloud-generic/kustomization.yaml b/deploy/cloud-generic/kustomization.yaml index d0a6060e8..6f43d24a2 100644 --- a/deploy/cloud-generic/kustomization.yaml +++ b/deploy/cloud-generic/kustomization.yaml @@ -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 diff --git a/docs/deploy/upgrade.md b/docs/deploy/upgrade.md index 195ab08f6..fd7a08023 100644 --- a/docs/deploy/upgrade.md +++ b/docs/deploy/upgrade.md @@ -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`. diff --git a/docs/examples/grpc/README.md b/docs/examples/grpc/README.md index b2b337384..ee6f42e70 100644 --- a/docs/examples/grpc/README.md +++ b/docs/examples/grpc/README.md @@ -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` @@ -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`. diff --git a/docs/examples/static-ip/nginx-ingress-controller.yaml b/docs/examples/static-ip/nginx-ingress-controller.yaml index 11ee45f33..fca0e2ab2 100644 --- a/docs/examples/static-ip/nginx-ingress-controller.yaml +++ b/docs/examples/static-ip/nginx-ingress-controller.yaml @@ -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: