Enable v1.30 in Ubuntu by updating the README

This commit adds the annotation parameter inside the ingress example in the "Ingress NGINX" README paragraph. This is not needed while using EL distributions, but without it Ubuntu ingresses won't work, as explained in this issue [1]. Fixes: #1 [1] kubernetes/ingress-nginx#8081
mmul-it · May 31, 2024 · 4576b70 · 4576b70
1 parent c7bdf7c
commit 4576b70
Showing 1 changed file with 9 additions and 2 deletions.
diff --git a/README.md b/README.md
@@ -417,7 +417,9 @@ deployment.apps/demo created
 $ kubectl expose deployment demo
 service/demo exposed
 
-$ kubectl create ingress demo --class=nginx --rule="demo.192.168.122.199.nip.io/*=demo:80"
+$ kubectl create ingress demo --class=nginx \
+    --rule="demo.192.168.122.199.nip.io/*=demo:80" \
+    --annotation="nginx.ingress.kubernetes.io/service-upstream=true"
 ingress.networking.k8s.io/demo created
 
 $ curl http://demo.192.168.122.199.nip.io
@@ -446,13 +448,18 @@ subject=CN = demo.192.168.122.199.nip.io
 $ kubectl create secret tls tls-secret --cert=./cert.crt --key=./cert.key
 secret/tls-secret created
 
-$ kubectl create ingress demo --class=nginx --rule="demo.192.168.122.199.nip.io/*=demo:80,tls=tls-secret"
+$ kubectl create ingress demo --class=nginx \
+    --rule="demo.192.168.122.199.nip.io/*=demo:80,tls=tls-secret" \
+    --annotation="nginx.ingress.kubernetes.io/service-upstream=true"
 ingress.networking.k8s.io/demo created
 
 $ curl -k https://demo.192.168.122.199.nip.io
 <html><body><h1>It works!</h1></body></html>
 ```
 
+The reason why the `--annotation="nginx.ingress.kubernetes.io/service-upstream=true"`
+is needed in explained in this [ingress-nginx issue](https://github.com/kubernetes/ingress-nginx/issues/8081).
+
 #### Ingress NGINX with MetalLB
 
 Another way is to use it in combination with MetalLB, by declaring a