feat: rename networking.k8s.io/v1beta1 to networking.k8s.io/v1

docs/content/providers/kubernetes-ingress.md

@@ -36,10 +36,10 @@ and derives the corresponding dynamic configuration from it,
 which in turn creates the resulting routers, services, handlers, etc.
 
 ```yaml tab="Ingress"
+apiVersion: networking.k8s.io/v1
 kind: Ingress
-apiVersion: networking.k8s.io/v1beta1
 metadata:
-  name: "foo"
+  name: foo
   namespace: production
 
 spec:
@@ -48,20 +48,26 @@ spec:
       http:
         paths:
           - path: /bar
+            pathType: Exact
             backend:
-              serviceName: service1
+              service:
-              servicePort: 80
+                name:  service1
+                port:
+                  number: 80
           - path: /foo
+            pathType: Exact
             backend:
-              serviceName: service1
+              service:
-              servicePort: 80
+                name:  service1
+                port:
+                  number: 80
 ```
 
-```yaml tab="Ingress Kubernetes v1.19+"
+```yaml tab="Ingress v1beta1 (deprecated)"
+apiVersion: networking.k8s.io/v1beta1
 kind: Ingress
-apiVersion: networking.k8s.io/v1
 metadata:
-  name: "foo"
+  name: foo
   namespace: production
 
 spec:
@@ -70,19 +76,13 @@ spec:
       http:
         paths:
           - path: /bar
-            pathType: Exact
             backend:
-              service:
+              serviceName: service1
-                name:  service1
+              servicePort: 80
-                port:
-                  number: 80
           - path: /foo
-            pathType: Exact
             backend:
-              service:
+              serviceName: service1
-                name:  service1
+              servicePort: 80
-                port:
-                  number: 80
 ```
 
 ## LetsEncrypt Support with the Ingress Provider
@@ -272,19 +272,19 @@ Otherwise, Ingresses missing the annotation, having an empty value, or the value
     ```
 
     ```yaml tab="Ingress"
-    apiVersion: "networking.k8s.io/v1beta1"
+    apiVersion: networking.k8s.io/v1beta1
-    kind: "Ingress"
+    kind: Ingress
     metadata:
-      name: "example-ingress"
+      name: example-ingress
     spec:
-      ingressClassName: "traefik-lb"
+      ingressClassName: traefik-lb
       rules:
       - host: "*.example.com"
         http:
           paths:
-          - path: "/example"
+          - path: /example
             backend:
-              serviceName: "example-service"
+              serviceName: example-service
               servicePort: 80
     ```
 
@@ -303,21 +303,21 @@ Otherwise, Ingresses missing the annotation, having an empty value, or the value
     ```
 
     ```yaml tab="Ingress"
-    apiVersion: "networking.k8s.io/v1"
+    apiVersion: networking.k8s.io/v1
-    kind: "Ingress"
+    kind: Ingress
     metadata:
-      name: "example-ingress"
+      name: example-ingress
     spec:
-      ingressClassName: "traefik-lb"
+      ingressClassName: traefik-lb
       rules:
       - host: "*.example.com"
         http:
           paths:
-          - path: "/example"
+          - path: /example
             pathType: Exact
             backend:
               service:
-                name: "example-service"
+                name: example-service
                 port:
                     number: 80
     ```

docs/content/reference/dynamic-configuration/kubernetes-crd-rbac.yml

@@ -1,5 +1,5 @@
+apiVersion: rbac.authorization.k8s.io/v1
 kind: ClusterRole
-apiVersion: rbac.authorization.k8s.io/v1beta1
 metadata:
   name: traefik-ingress-controller
 
@@ -48,8 +48,8 @@ rules:
       - watch
 
 ---
+apiVersion: rbac.authorization.k8s.io/v1
 kind: ClusterRoleBinding
-apiVersion: rbac.authorization.k8s.io/v1beta1
 metadata:
   name: traefik-ingress-controller
 

docs/content/reference/dynamic-configuration/kubernetes-gateway-rbac.yml

@@ -38,8 +38,8 @@ rules:
       - update
 
 ---
+apiVersion: rbac.authorization.k8s.io/v1
 kind: ClusterRoleBinding
-apiVersion: rbac.authorization.k8s.io/v1beta1
 metadata:
   name: gateway-controller
 

docs/content/routing/providers/kubernetes-ingress.md

@@ -15,8 +15,8 @@ which in turn will create the resulting routers, services, handlers, etc.
 
     ```yaml tab="RBAC"
     ---
+    apiVersion: rbac.authorization.k8s.io/v1
     kind: ClusterRole
-    apiVersion: rbac.authorization.k8s.io/v1beta1
     metadata:
       name: traefik-ingress-controller
     rules:
@@ -48,8 +48,8 @@ which in turn will create the resulting routers, services, handlers, etc.
           - update
 
     ---
+    apiVersion: rbac.authorization.k8s.io/v1
     kind: ClusterRoleBinding
-    apiVersion: rbac.authorization.k8s.io/v1beta1
     metadata:
       name: traefik-ingress-controller
     roleRef:
@@ -63,8 +63,8 @@ which in turn will create the resulting routers, services, handlers, etc.
     ```
 
     ```yaml tab="Ingress"
+    apiVersion: networking.k8s.io/v1
     kind: Ingress
-    apiVersion: networking.k8s.io/v1beta1
     metadata:
       name: myingress
       annotations:
@@ -76,18 +76,24 @@ which in turn will create the resulting routers, services, handlers, etc.
           http:
             paths:
               - path: /bar
+                pathType: Exact
                 backend:
-                  serviceName: whoami
+                  service:
-                  servicePort: 80
+                    name:  whoami
+                    port:
+                      number: 80
               - path: /foo
+                pathType: Exact
                 backend:
-                  serviceName: whoami
+                  service:
-                  servicePort: 80
+                    name:  whoami
+                    port:
+                      number: 80
     ```
 
-    ```yaml tab="Ingress Kubernetes v1.19+"
+    ```yaml tab="Ingress v1beta1 (deprecated)"
+    apiVersion: networking.k8s.io/v1beta1
     kind: Ingress
-    apiVersion: networking.k8s.io/v1
     metadata:
       name: myingress
       annotations:
@@ -99,19 +105,13 @@ which in turn will create the resulting routers, services, handlers, etc.
           http:
             paths:
               - path: /bar
-                pathType: Exact
                 backend:
-                  service:
+                  serviceName: whoami
-                    name:  whoami
+                  servicePort: 80
-                    port:
-                      number: 80
               - path: /foo
-                pathType: Exact
                 backend:
-                  service:
+                  serviceName: whoami
-                    name:  whoami
+                  servicePort: 80
-                    port:
-                      number: 80
     ```
 
     ```yaml tab="Traefik"
@@ -121,8 +121,8 @@ which in turn will create the resulting routers, services, handlers, etc.
       name: traefik-ingress-controller
 
     ---
-    kind: Deployment
     apiVersion: apps/v1
+    kind: Deployment
     metadata:
       name: traefik
       labels:
@@ -166,8 +166,8 @@ which in turn will create the resulting routers, services, handlers, etc.
     ```
 
     ```yaml tab="Whoami"
-    kind: Deployment
     apiVersion: apps/v1
+    kind: Deployment
     metadata:
       name: whoami
       labels:
@@ -401,8 +401,8 @@ This way, any Ingress attached to this Entrypoint will have TLS termination by d
 
     ```yaml tab="RBAC"
     ---
+    apiVersion: rbac.authorization.k8s.io/v1
     kind: ClusterRole
-    apiVersion: rbac.authorization.k8s.io/v1beta1
     metadata:
       name: traefik-ingress-controller
     rules:
@@ -434,8 +434,8 @@ This way, any Ingress attached to this Entrypoint will have TLS termination by d
           - update
 
     ---
+    apiVersion: rbac.authorization.k8s.io/v1
     kind: ClusterRoleBinding
-    apiVersion: rbac.authorization.k8s.io/v1beta1
     metadata:
       name: traefik-ingress-controller
     roleRef:
@@ -449,8 +449,8 @@ This way, any Ingress attached to this Entrypoint will have TLS termination by d
     ```
 
     ```yaml tab="Ingress"
+    apiVersion: networking.k8s.io/v1
     kind: Ingress
-    apiVersion: networking.k8s.io/v1beta1
     metadata:
       name: myingress
       annotations:
@@ -462,18 +462,24 @@ This way, any Ingress attached to this Entrypoint will have TLS termination by d
           http:
             paths:
               - path: /bar
+                pathType: Exact
                 backend:
-                  serviceName: whoami
+                  service:
-                  servicePort: 80
+                    name:  whoami
+                    port:
+                      number: 80
               - path: /foo
+                pathType: Exact
                 backend:
-                  serviceName: whoami
+                  service:
-                  servicePort: 80
+                    name:  whoami
+                    port:
+                      number: 80
     ```
 
-    ```yaml tab="Ingress Kubernetes v1.19+"
+    ```yaml tab="Ingress v1beta1 (deprecated)"
+    apiVersion: networking.k8s.io/v1beta1
     kind: Ingress
-    apiVersion: networking.k8s.io/v1
     metadata:
       name: myingress
       annotations:
@@ -485,19 +491,13 @@ This way, any Ingress attached to this Entrypoint will have TLS termination by d
           http:
             paths:
               - path: /bar
-                pathType: Exact
                 backend:
-                  service:
+                  serviceName: whoami
-                    name:  whoami
+                  servicePort: 80
-                    port:
-                      number: 80
               - path: /foo
-                pathType: Exact
                 backend:
-                  service:
+                  serviceName: whoami
-                    name:  whoami
+                  servicePort: 80
-                    port:
-                      number: 80
     ```
 
     ```yaml tab="Traefik"
@@ -507,8 +507,8 @@ This way, any Ingress attached to this Entrypoint will have TLS termination by d
       name: traefik-ingress-controller
 
     ---
-    kind: Deployment
     apiVersion: apps/v1
+    kind: Deployment
     metadata:
       name: traefik
       labels:
@@ -553,8 +553,8 @@ This way, any Ingress attached to this Entrypoint will have TLS termination by d
     ```
 
     ```yaml tab="Whoami"
-    kind: Deployment
     apiVersion: apps/v1
+    kind: Deployment
     metadata:
       name: whoami
       labels:
@@ -608,8 +608,8 @@ For more options, please refer to the available [annotations](#on-ingress).
 
     ```yaml tab="RBAC"
     ---
+    apiVersion: rbac.authorization.k8s.io/v1
     kind: ClusterRole
-    apiVersion: rbac.authorization.k8s.io/v1beta1
     metadata:
       name: traefik-ingress-controller
     rules:
@@ -641,8 +641,8 @@ For more options, please refer to the available [annotations](#on-ingress).
           - update
 
     ---
+    apiVersion: rbac.authorization.k8s.io/v1
     kind: ClusterRoleBinding
-    apiVersion: rbac.authorization.k8s.io/v1beta1
     metadata:
       name: traefik-ingress-controller
     roleRef:
@@ -656,8 +656,8 @@ For more options, please refer to the available [annotations](#on-ingress).
     ```
 
     ```yaml tab="Ingress"
+    apiVersion: networking.k8s.io/v1
     kind: Ingress
-    apiVersion: networking.k8s.io/v1beta1
     metadata:
       name: myingress
       annotations:
@@ -670,18 +670,24 @@ For more options, please refer to the available [annotations](#on-ingress).
           http:
             paths:
               - path: /bar
+                pathType: Exact
                 backend:
-                  serviceName: whoami
+                  service:
-                  servicePort: 80
+                    name:  whoami
+                    port:
+                      number: 80
               - path: /foo
+                pathType: Exact
                 backend:
-                  serviceName: whoami
+                  service:
-                  servicePort: 80
+                    name:  whoami
+                    port:
+                      number: 80
     ```
 
-    ```yaml tab="Ingress Kubernetes v1.19+"
+    ```yaml tab="Ingress v1beta1 (deprecated)"
+    apiVersion: networking.k8s.io/v1beta1
     kind: Ingress
-    apiVersion: networking.k8s.io/v1
     metadata:
       name: myingress
       annotations:
@@ -694,19 +700,13 @@ For more options, please refer to the available [annotations](#on-ingress).
           http:
             paths:
               - path: /bar
-                pathType: Exact
                 backend:
-                  service:
+                  serviceName: whoami
-                    name:  whoami
+                  servicePort: 80
-                    port:
-                      number: 80
               - path: /foo
-                pathType: Exact
                 backend:
-                  service:
+                  serviceName: whoami
-                    name:  whoami
+                  servicePort: 80
-                    port:
-                      number: 80
     ```
 
     ```yaml tab="Traefik"
@@ -716,8 +716,8 @@ For more options, please refer to the available [annotations](#on-ingress).
       name: traefik-ingress-controller
 
     ---
-    kind: Deployment
     apiVersion: apps/v1
+    kind: Deployment
     metadata:
       name: traefik
       labels:
@@ -761,8 +761,8 @@ For more options, please refer to the available [annotations](#on-ingress).
     ```
 
     ```yaml tab="Whoami"
-    kind: Deployment
     apiVersion: apps/v1
+    kind: Deployment
     metadata:
       name: whoami
       labels:
@@ -807,31 +807,8 @@ For more options, please refer to the available [annotations](#on-ingress).
 ??? example "Using a secret"
 
     ```yaml tab="Ingress"
-    kind: Ingress
-    apiVersion: networking.k8s.io/v1beta1
-    metadata:
-      name: foo
-      namespace: production
-
-    spec:
-      rules:
-      - host: example.net
-        http:
-          paths:
-          - path: /bar
-            backend:
-              serviceName: service1
-              servicePort: 80
-      # Only selects which certificate(s) should be loaded from the secret, in order to terminate TLS.
-      # Doesn't enable TLS for that ingress (hence for the underlying router).
-      # Please see the TLS annotations on ingress made for that purpose.
-      tls:
-      - secretName: supersecret
-    ```
-
-    ```yaml tab="Ingress Kubernetes v1.19+"
-    kind: Ingress
     apiVersion: networking.k8s.io/v1
+    kind: Ingress
     metadata:
       name: foo
       namespace: production
@@ -855,6 +832,29 @@ For more options, please refer to the available [annotations](#on-ingress).
       - secretName: supersecret
     ```
 
+    ```yaml tab="Ingress v1beta1 (deprecated)"
+    apiVersion: networking.k8s.io/v1beta1
+    kind: Ingress
+    metadata:
+      name: foo
+      namespace: production
+
+    spec:
+      rules:
+      - host: example.net
+        http:
+          paths:
+          - path: /bar
+            backend:
+              serviceName: service1
+              servicePort: 80
+      # Only selects which certificate(s) should be loaded from the secret, in order to terminate TLS.
+      # Doesn't enable TLS for that ingress (hence for the underlying router).
+      # Please see the TLS annotations on ingress made for that purpose.
+      tls:
+      - secretName: supersecret
+    ```
+
     ```yaml tab="Secret"
     apiVersion: v1
     kind: Secret
@@ -900,18 +900,6 @@ and will connect via TLS automatically.
 Ingresses can be created that look like the following:
 
 ```yaml tab="Ingress"
-apiVersion: networking.k8s.io/v1beta1
-kind: Ingress
-metadata:
- name: cheese
-
-spec:
-  defaultBackend:
-    serviceName: stilton
-    serverPort: 80
-```
-
-```yaml tab="Ingress Kubernetes v1.19+"
 apiVersion: networking.k8s.io/v1
 kind: Ingress
 metadata:
@@ -925,6 +913,18 @@ spec:
         number: 80
 ```
 
+```yaml tab="Ingress v1beta1 (deprecated)"
+apiVersion: networking.k8s.io/v1beta1
+kind: Ingress
+metadata:
+ name: cheese
+
+spec:
+  defaultBackend:
+    serviceName: stilton
+    serverPort: 80
+```
+
 This ingress follows the Global Default Backend property of ingresses.
 This will allow users to create a "default router" that will match all unmatched requests.