Skip to content

Commit

Permalink
docs: fix incorrect command for getting ingressroutetcp resources (#1778
Browse files Browse the repository at this point in the history
)
  • Loading branch information
kurokobo authored Apr 6, 2024
1 parent 7b02b5d commit 413b700
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/user-guide/advanced-configuration/mesh-ingress.md
Original file line number Diff line number Diff line change
Expand Up @@ -86,7 +86,7 @@ spec:
!!! tip
AWX Operator supports both API groups `traefik.io` and `traefik.containo.us` in `ingress_api_version` for Traefik, but it is recommended to use `traefik.io` since `traefik.containo.us` is deprecated in Traefik v2.10 and is removed in Traefik v3. Refer to [Traefik documentation](https://doc.traefik.io/traefik/migration/v2/#v210) for more information about deprecation.

If you can't see any IngressRouteTCP resources by `kubectl` command after deploying mesh ingress, you should fully qualify the resource name with API group, `kubectl get ingressroutetcp.traefik.io` or `kubectl get traefik.containo.us` for example.
If you can't see any IngressRouteTCP resources by `kubectl` command after deploying mesh ingress, you should fully qualify the resource name with API group, `kubectl get ingressroutetcp.traefik.io` or `kubectl get ingressroutetcp.traefik.containo.us` for example.

### On Kubernetes with User managed Ingress

Expand Down

0 comments on commit 413b700

Please sign in to comment.