Support 'networking.k8s.io/v1beta1' ingress apiVersion

docs/content/migration/v1-to-v2.md

@@ -40,7 +40,7 @@ Then any router can refer to an instance of the wanted middleware.
     ```
 
     ```yaml tab="K8s Ingress"
-    apiVersion: extensions/v1beta1
+    apiVersion: networking.k8s.io/v1beta1
     kind: Ingress
     metadata:
       name: traefik

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

@@ -24,7 +24,7 @@ The Kubernetes Ingress Controller, The Custom Resource Way.
     
     ---
     kind: Deployment
-    apiVersion: extensions/v1beta1
+    apiVersion: apps/v1
     metadata:
       name: traefik
       labels:
@@ -97,7 +97,7 @@ The Kubernetes Ingress Controller, The Custom Resource Way.
 
     ```yaml tab="Whoami"
     kind: Deployment
-    apiVersion: extensions/v1beta1
+    apiVersion: apps/v1
     metadata:
       name: whoami
       namespace: default

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

@@ -11,7 +11,7 @@ which in turn will create the resulting routers, services, handlers, etc.
 
 ```yaml
 kind: Ingress
-apiVersion: extensions/v1beta1
+apiVersion: networking.k8s.io/v1beta1
 metadata:
   name: foo
   namespace: production
@@ -40,7 +40,7 @@ spec:
     
     ```yaml tab="Ingress"
     kind: Ingress
-    apiVersion: extensions/v1beta1
+    apiVersion: networking.k8s.io/v1beta1
     metadata:
       name: foo
       namespace: production
@@ -234,7 +234,7 @@ and will connect via TLS automatically.
     
     ```yaml tab="Ingress"
     kind: Ingress
-    apiVersion: extensions/v1beta1
+    apiVersion: networking.k8s.io/v1beta1
     metadata:
       name: foo
       namespace: production
@@ -276,7 +276,7 @@ TLS certificates can be managed in Secrets objects.
 Ingresses can be created that look like the following:
 
 ```yaml
-apiVersion: extensions/v1beta1
+apiVersion: networking.k8s.io/v1beta1
 kind: Ingress
 metadata:
  name: cheese