Fix image version (#4977)

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

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`.

docs/examples/grpc/README.md

@@ -13,7 +13,7 @@ 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

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: