Deploy GitHub Pages

examples/grpc/index.html

@@ -1302,7 +1302,7 @@ nginx controller.</p>
    for the ingress).</li>
 <li>You have the nginx-ingress controller installed in typical fashion (must be
    at least
-   <a href="https://quay.io/kubernetes-ingress-controller/nginx-ingress-controller">quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.29.0</a>
+   <a href="https://quay.io/kubernetes-ingress-controller/nginx-ingress-controller">quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.30.0</a>
    for grpc support.</li>
 <li>You have a backend application running a gRPC server and listening for TCP
    traffic.  If you prefer, you can use the

examples/psp/index.html

@@ -1160,7 +1160,7 @@ you will need to provide the Deployment with the permissions to create pods.</p>
 <div class="codehilite"><pre><span></span><code><span class="go">kubectl apply -f https://raw.githubusercontent.com/kubernetes/ingress-nginx/master/docs/examples/psp/psp.yaml</span>
 </code></pre></div></p>
 <p>Now that the pod security policy is applied, we can continue as usual by applying the
-<a href="https://raw.githubusercontent.com/kubernetes/ingress-nginx/nginx-0.29.0/deploy/static/mandatory.yaml">mandatory.yaml</a>
+<a href="https://raw.githubusercontent.com/kubernetes/ingress-nginx/nginx-0.30.0/deploy/static/mandatory.yaml">mandatory.yaml</a>
 according to the <a href="../../deploy/">Installation Guide</a>.</p>
 <p>Note: PSP permissions must be granted before to the creation of the Deployment and the ReplicaSet.
 If the Deployment or ReplicaSet already exist, they will receive the PSP permissions

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.29.0
+      - image: quay.io/kubernetes-ingress-controller/nginx-ingress-controller:0.30.0
         name: nginx-ingress-controller
         readinessProbe:
           httpGet: