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

Fix image version (#4977)

Browse source
This commit is contained in:
Manuel Alejandro de Brito Fontes 2020-01-28 08:56:12 -03:00 committed by GitHub
parent 0c9ff1afed
commit 19e9e9d7ed
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
4 changed files with 6 additions and 6 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
deploy/cloud-generic/kustomization.yaml
View file

@ -12,7 +12,7 @@ resources:
- service.yaml - service.yaml
images: images:
- name: quay.io/kubernetes-ingress-controller/nginx-ingress-controller - name: quay.io/kubernetes-ingress-controller/nginx-ingress-controller
newTag: master newTag: 0.28.0
vars: vars:
- fieldref: - fieldref:
fieldPath: metadata.name fieldPath: metadata.name

2
docs/deploy/upgrade.md
View file

@ -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 \ 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`. For interactive editing, use `kubectl edit deployment nginx-ingress-controller`.

2
docs/examples/grpc/README.md
View file

@ -13,7 +13,7 @@ nginx controller.
for the ingress). for the ingress).
3. You have the nginx-ingress controller installed in typical fashion (must be 3. You have the nginx-ingress controller installed in typical fashion (must be
at least 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. for grpc support.
4. You have a backend application running a gRPC server and listening for TCP 4. You have a backend application running a gRPC server and listening for TCP
traffic. If you prefer, you can use the traffic. If you prefer, you can use the

2
docs/examples/static-ip/nginx-ingress-controller.yaml
View file

@ -24,7 +24,7 @@ spec:
# hostNetwork: true # hostNetwork: true
terminationGracePeriodSeconds: 60 terminationGracePeriodSeconds: 60
containers: 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 name: nginx-ingress-controller
readinessProbe: readinessProbe:
httpGet: httpGet: