Merge v2.10 into v3.0
This commit is contained in:
commit
286181aa61
62 changed files with 712 additions and 189 deletions
|
@ -2011,4 +2011,4 @@ If the ServersTransportTCP CRD is defined in another provider the cross-provider
|
|||
|
||||
Also see the [full example](../../user-guides/crd-acme/index.md) with Let's Encrypt.
|
||||
|
||||
{!traefik-api-management-kubernetes.md!}
|
||||
{!traefik-for-business-applications.md!}
|
||||
|
|
|
@ -355,4 +355,4 @@ Kubernetes cluster before creating `TLSRoute` objects.
|
|||
| [11] | `group` | Group is the group of the referent. Only `traefik.io` and `gateway.networking.k8s.io` values are supported. |
|
||||
| [12] | `kind` | Kind is kind of the referent. Only `TraefikService` and `Service` values are supported. |
|
||||
|
||||
{!traefik-api-management-kubernetes.md!}
|
||||
{!traefik-for-business-applications.md!}
|
||||
|
|
|
@ -864,4 +864,4 @@ This will allow users to create a "default router" that will match all unmatched
|
|||
|
||||
To do this, use the `traefik.ingress.kubernetes.io/router.priority` annotation (as seen in [Annotations on Ingress](#on-ingress)) on your ingresses accordingly.
|
||||
|
||||
{!traefik-api-management-kubernetes.md!}
|
||||
{!traefik-for-business-applications.md!}
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue