diff --git a/docs/troubleshooting/other-troubleshooting-tips/kubernetes-resources.md b/docs/troubleshooting/other-troubleshooting-tips/kubernetes-resources.md index 635e4d07371..c79927b39c2 100644 --- a/docs/troubleshooting/other-troubleshooting-tips/kubernetes-resources.md +++ b/docs/troubleshooting/other-troubleshooting-tips/kubernetes-resources.md @@ -78,22 +78,22 @@ kubectl -n kube-system get endpoints kube-scheduler -o jsonpath='{.metadata.anno ## Ingress Controller -The default Ingress Controller is NGINX and is deployed as a DaemonSet in the `ingress-nginx` namespace. The pods are only scheduled to nodes with the `worker` role. +The default Ingress Controller is Traefik and is deployed as a DaemonSet in the `traefik` namespace. The pods are only scheduled to nodes with the `worker` role. Check if the pods are running on all nodes: ``` -kubectl -n ingress-nginx get pods -o wide +kubectl -n traefik get pods -o wide ``` Example output: ``` -kubectl -n ingress-nginx get pods -o wide +kubectl -n traefik get pods -o wide NAME READY STATUS RESTARTS AGE IP NODE default-http-backend-797c5bc547-kwwlq 1/1 Running 0 17m x.x.x.x worker-1 -nginx-ingress-controller-4qd64 1/1 Running 0 14m x.x.x.x worker-1 -nginx-ingress-controller-8wxhm 1/1 Running 0 13m x.x.x.x worker-0 +traefik-4qd64 1/1 Running 0 14m x.x.x.x worker-1 +traefik-8wxhm 1/1 Running 0 13m x.x.x.x worker-0 ``` If a pod is unable to run (Status is not **Running**, Ready status is not showing `1/1` or you see a high count of Restarts), check the pod details, logs and namespace events. @@ -101,27 +101,27 @@ If a pod is unable to run (Status is not **Running**, Ready status is not showin ### Pod details ``` -kubectl -n ingress-nginx describe pods -l app=ingress-nginx +kubectl -n traefik describe pods -l app=traefik ``` ### Pod container logs -The below command can show the logs of all the pods labeled "app=ingress-nginx", but it will display only 10 lines of log because of the restrictions of the `kubectl logs` command. Refer to `--tail` of `kubectl logs -h` for more information. +The below command can show the logs of all the pods labeled "app=traefik", but it will display only 10 lines of log because of the restrictions of the `kubectl logs` command. Refer to `--tail` of `kubectl logs -h` for more information. ``` -kubectl -n ingress-nginx logs -l app=ingress-nginx +kubectl -n traefik logs -l app=traefik ``` If the full log is needed, specify the pod name in the trailing command: ``` -kubectl -n ingress-nginx logs +kubectl -n traefik logs ``` ### Namespace events ``` -kubectl -n ingress-nginx get events +kubectl -n traefik get events ``` ### Debug logging @@ -129,7 +129,7 @@ kubectl -n ingress-nginx get events To enable debug logging: ``` -kubectl -n ingress-nginx patch ds nginx-ingress-controller --type='json' -p='[{"op": "add", "path": "/spec/template/spec/containers/0/args/-", "value": "--v=5"}]' +kubectl -n traefik patch ds traefik --type='json' -p='[{"op": "add", "path": "/spec/template/spec/containers/0/args/-", "value": "--v=5"}]' ``` ### Check configuration @@ -137,7 +137,7 @@ kubectl -n ingress-nginx patch ds nginx-ingress-controller --type='json' -p='[{" Retrieve generated configuration in each pod: ``` -kubectl -n ingress-nginx get pods -l app=ingress-nginx --no-headers -o custom-columns=.NAME:.metadata.name | while read pod; do kubectl -n ingress-nginx exec $pod -- cat /etc/nginx/nginx.conf; done +kubectl -n traefik get pods -l app=traefik --no-headers -o custom-columns=.NAME:.metadata.name | while read pod; do kubectl -n traefik exec $pod -- cat /etc/nginx/nginx.conf; done ``` ## Rancher agents diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/troubleshooting/other-troubleshooting-tips/kubernetes-resources.md b/i18n/zh/docusaurus-plugin-content-docs/current/troubleshooting/other-troubleshooting-tips/kubernetes-resources.md index 6fee94b2cb4..db4b79ae3d8 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/current/troubleshooting/other-troubleshooting-tips/kubernetes-resources.md +++ b/i18n/zh/docusaurus-plugin-content-docs/current/troubleshooting/other-troubleshooting-tips/kubernetes-resources.md @@ -74,22 +74,22 @@ kubectl -n kube-system get endpoints kube-scheduler -o jsonpath='{.metadata.anno ## Ingress Controller -默认的 Ingress Controller 是 NGINX，作为 DaemonSet 部署在 `ingress-nginx` 命名空间中。Pod 仅会调度到具有 `worker` 角色的节点。 +默认的 Ingress Controller 是 Traefik，作为 DaemonSet 部署在 `traefik` 命名空间中。Pod 仅会调度到具有 `worker` 角色的节点。 检查 pod 是否运行在所有节点上： ``` -kubectl -n ingress-nginx get pods -o wide +kubectl -n traefik get pods -o wide ``` 输出示例： ``` -kubectl -n ingress-nginx get pods -o wide +kubectl -n traefik get pods -o wide NAME READY STATUS RESTARTS AGE IP NODE default-http-backend-797c5bc547-kwwlq 1/1 Running 0 17m x.x.x.x worker-1 -nginx-ingress-controller-4qd64 1/1 Running 0 14m x.x.x.x worker-1 -nginx-ingress-controller-8wxhm 1/1 Running 0 13m x.x.x.x worker-0 +traefik-4qd64 1/1 Running 0 14m x.x.x.x worker-1 +traefik-8wxhm 1/1 Running 0 13m x.x.x.x worker-0 ``` 如果 pod 无法运行（即状态不是 **Running**，Ready 状态未显示 `1/1`，或者有大量 Restarts），请检查 pod 详细信息，日志和命名空间事件。 @@ -97,27 +97,27 @@ nginx-ingress-controller-8wxhm 1/1 Running 0 13m ### Pod 详细信息 ``` -kubectl -n ingress-nginx describe pods -l app=ingress-nginx +kubectl -n traefik describe pods -l app=traefik ``` ### Pod 容器日志 -下面的命令可以显示所有标记为 “app=ingress-nginx” 的 pod 的日志，但是由于 `kubectl logs` 命令的限制，它只会显示 10 行日志。有关详细信息，请参阅 `kubectl logs -h` 的 `--tail`。 +下面的命令可以显示所有标记为 “app=traefik” 的 pod 的日志，但是由于 `kubectl logs` 命令的限制，它只会显示 10 行日志。有关详细信息，请参阅 `kubectl logs -h` 的 `--tail`。 ``` -kubectl -n ingress-nginx logs -l app=ingress-nginx +kubectl -n traefik logs -l app=traefik ``` 如果需要查看完整的日志，请在命令中尾随 pod 名称： ``` -kubectl -n ingress-nginx logs +kubectl -n traefik logs ``` ### 命名空间事件 ``` -kubectl -n ingress-nginx get events +kubectl -n traefik get events ``` ### 调试日志 @@ -125,7 +125,7 @@ kubectl -n ingress-nginx get events 要启用调试日志： ``` -kubectl -n ingress-nginx patch ds nginx-ingress-controller --type='json' -p='[{"op": "add", "path": "/spec/template/spec/containers/0/args/-", "value": "--v=5"}]' +kubectl -n traefik patch ds traefik --type='json' -p='[{"op": "add", "path": "/spec/template/spec/containers/0/args/-", "value": "--v=5"}]' ``` ### 检查配置 @@ -133,7 +133,7 @@ kubectl -n ingress-nginx patch ds nginx-ingress-controller --type='json' -p='[{" 在每个 pod 中检索生成的配置： ``` -kubectl -n ingress-nginx get pods -l app=ingress-nginx --no-headers -o custom-columns=.NAME:.metadata.name | while read pod; do kubectl -n ingress-nginx exec $pod -- cat /etc/nginx/nginx.conf; done +kubectl -n traefik get pods -l app=traefik --no-headers -o custom-columns=.NAME:.metadata.name | while read pod; do kubectl -n traefik exec $pod -- cat /etc/nginx/nginx.conf; done ``` ## Rancher Agents diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.10/troubleshooting/other-troubleshooting-tips/kubernetes-resources.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.10/troubleshooting/other-troubleshooting-tips/kubernetes-resources.md index 6fee94b2cb4..db4b79ae3d8 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/version-2.10/troubleshooting/other-troubleshooting-tips/kubernetes-resources.md +++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.10/troubleshooting/other-troubleshooting-tips/kubernetes-resources.md @@ -74,22 +74,22 @@ kubectl -n kube-system get endpoints kube-scheduler -o jsonpath='{.metadata.anno ## Ingress Controller -默认的 Ingress Controller 是 NGINX，作为 DaemonSet 部署在 `ingress-nginx` 命名空间中。Pod 仅会调度到具有 `worker` 角色的节点。 +默认的 Ingress Controller 是 Traefik，作为 DaemonSet 部署在 `traefik` 命名空间中。Pod 仅会调度到具有 `worker` 角色的节点。 检查 pod 是否运行在所有节点上： ``` -kubectl -n ingress-nginx get pods -o wide +kubectl -n traefik get pods -o wide ``` 输出示例： ``` -kubectl -n ingress-nginx get pods -o wide +kubectl -n traefik get pods -o wide NAME READY STATUS RESTARTS AGE IP NODE default-http-backend-797c5bc547-kwwlq 1/1 Running 0 17m x.x.x.x worker-1 -nginx-ingress-controller-4qd64 1/1 Running 0 14m x.x.x.x worker-1 -nginx-ingress-controller-8wxhm 1/1 Running 0 13m x.x.x.x worker-0 +traefik-4qd64 1/1 Running 0 14m x.x.x.x worker-1 +traefik-8wxhm 1/1 Running 0 13m x.x.x.x worker-0 ``` 如果 pod 无法运行（即状态不是 **Running**，Ready 状态未显示 `1/1`，或者有大量 Restarts），请检查 pod 详细信息，日志和命名空间事件。 @@ -97,27 +97,27 @@ nginx-ingress-controller-8wxhm 1/1 Running 0 13m ### Pod 详细信息 ``` -kubectl -n ingress-nginx describe pods -l app=ingress-nginx +kubectl -n traefik describe pods -l app=traefik ``` ### Pod 容器日志 -下面的命令可以显示所有标记为 “app=ingress-nginx” 的 pod 的日志，但是由于 `kubectl logs` 命令的限制，它只会显示 10 行日志。有关详细信息，请参阅 `kubectl logs -h` 的 `--tail`。 +下面的命令可以显示所有标记为 “app=traefik” 的 pod 的日志，但是由于 `kubectl logs` 命令的限制，它只会显示 10 行日志。有关详细信息，请参阅 `kubectl logs -h` 的 `--tail`。 ``` -kubectl -n ingress-nginx logs -l app=ingress-nginx +kubectl -n traefik logs -l app=traefik ``` 如果需要查看完整的日志，请在命令中尾随 pod 名称： ``` -kubectl -n ingress-nginx logs +kubectl -n traefik logs ``` ### 命名空间事件 ``` -kubectl -n ingress-nginx get events +kubectl -n traefik get events ``` ### 调试日志 @@ -125,7 +125,7 @@ kubectl -n ingress-nginx get events 要启用调试日志： ``` -kubectl -n ingress-nginx patch ds nginx-ingress-controller --type='json' -p='[{"op": "add", "path": "/spec/template/spec/containers/0/args/-", "value": "--v=5"}]' +kubectl -n traefik patch ds traefik --type='json' -p='[{"op": "add", "path": "/spec/template/spec/containers/0/args/-", "value": "--v=5"}]' ``` ### 检查配置 @@ -133,7 +133,7 @@ kubectl -n ingress-nginx patch ds nginx-ingress-controller --type='json' -p='[{" 在每个 pod 中检索生成的配置： ``` -kubectl -n ingress-nginx get pods -l app=ingress-nginx --no-headers -o custom-columns=.NAME:.metadata.name | while read pod; do kubectl -n ingress-nginx exec $pod -- cat /etc/nginx/nginx.conf; done +kubectl -n traefik get pods -l app=traefik --no-headers -o custom-columns=.NAME:.metadata.name | while read pod; do kubectl -n traefik exec $pod -- cat /etc/nginx/nginx.conf; done ``` ## Rancher Agents diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.11/troubleshooting/other-troubleshooting-tips/kubernetes-resources.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.11/troubleshooting/other-troubleshooting-tips/kubernetes-resources.md index 6fee94b2cb4..db4b79ae3d8 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/version-2.11/troubleshooting/other-troubleshooting-tips/kubernetes-resources.md +++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.11/troubleshooting/other-troubleshooting-tips/kubernetes-resources.md @@ -74,22 +74,22 @@ kubectl -n kube-system get endpoints kube-scheduler -o jsonpath='{.metadata.anno ## Ingress Controller -默认的 Ingress Controller 是 NGINX，作为 DaemonSet 部署在 `ingress-nginx` 命名空间中。Pod 仅会调度到具有 `worker` 角色的节点。 +默认的 Ingress Controller 是 Traefik，作为 DaemonSet 部署在 `traefik` 命名空间中。Pod 仅会调度到具有 `worker` 角色的节点。 检查 pod 是否运行在所有节点上： ``` -kubectl -n ingress-nginx get pods -o wide +kubectl -n traefik get pods -o wide ``` 输出示例： ``` -kubectl -n ingress-nginx get pods -o wide +kubectl -n traefik get pods -o wide NAME READY STATUS RESTARTS AGE IP NODE default-http-backend-797c5bc547-kwwlq 1/1 Running 0 17m x.x.x.x worker-1 -nginx-ingress-controller-4qd64 1/1 Running 0 14m x.x.x.x worker-1 -nginx-ingress-controller-8wxhm 1/1 Running 0 13m x.x.x.x worker-0 +traefik-4qd64 1/1 Running 0 14m x.x.x.x worker-1 +traefik-8wxhm 1/1 Running 0 13m x.x.x.x worker-0 ``` 如果 pod 无法运行（即状态不是 **Running**，Ready 状态未显示 `1/1`，或者有大量 Restarts），请检查 pod 详细信息，日志和命名空间事件。 @@ -97,27 +97,27 @@ nginx-ingress-controller-8wxhm 1/1 Running 0 13m ### Pod 详细信息 ``` -kubectl -n ingress-nginx describe pods -l app=ingress-nginx +kubectl -n traefik describe pods -l app=traefik ``` ### Pod 容器日志 -下面的命令可以显示所有标记为 “app=ingress-nginx” 的 pod 的日志，但是由于 `kubectl logs` 命令的限制，它只会显示 10 行日志。有关详细信息，请参阅 `kubectl logs -h` 的 `--tail`。 +下面的命令可以显示所有标记为 “app=traefik” 的 pod 的日志，但是由于 `kubectl logs` 命令的限制，它只会显示 10 行日志。有关详细信息，请参阅 `kubectl logs -h` 的 `--tail`。 ``` -kubectl -n ingress-nginx logs -l app=ingress-nginx +kubectl -n traefik logs -l app=traefik ``` 如果需要查看完整的日志，请在命令中尾随 pod 名称： ``` -kubectl -n ingress-nginx logs +kubectl -n traefik logs ``` ### 命名空间事件 ``` -kubectl -n ingress-nginx get events +kubectl -n traefik get events ``` ### 调试日志 @@ -125,7 +125,7 @@ kubectl -n ingress-nginx get events 要启用调试日志： ``` -kubectl -n ingress-nginx patch ds nginx-ingress-controller --type='json' -p='[{"op": "add", "path": "/spec/template/spec/containers/0/args/-", "value": "--v=5"}]' +kubectl -n traefik patch ds traefik --type='json' -p='[{"op": "add", "path": "/spec/template/spec/containers/0/args/-", "value": "--v=5"}]' ``` ### 检查配置 @@ -133,7 +133,7 @@ kubectl -n ingress-nginx patch ds nginx-ingress-controller --type='json' -p='[{" 在每个 pod 中检索生成的配置： ``` -kubectl -n ingress-nginx get pods -l app=ingress-nginx --no-headers -o custom-columns=.NAME:.metadata.name | while read pod; do kubectl -n ingress-nginx exec $pod -- cat /etc/nginx/nginx.conf; done +kubectl -n traefik get pods -l app=traefik --no-headers -o custom-columns=.NAME:.metadata.name | while read pod; do kubectl -n traefik exec $pod -- cat /etc/nginx/nginx.conf; done ``` ## Rancher Agents diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.12/troubleshooting/other-troubleshooting-tips/kubernetes-resources.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.12/troubleshooting/other-troubleshooting-tips/kubernetes-resources.md index 6fee94b2cb4..db4b79ae3d8 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/version-2.12/troubleshooting/other-troubleshooting-tips/kubernetes-resources.md +++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.12/troubleshooting/other-troubleshooting-tips/kubernetes-resources.md @@ -74,22 +74,22 @@ kubectl -n kube-system get endpoints kube-scheduler -o jsonpath='{.metadata.anno ## Ingress Controller -默认的 Ingress Controller 是 NGINX，作为 DaemonSet 部署在 `ingress-nginx` 命名空间中。Pod 仅会调度到具有 `worker` 角色的节点。 +默认的 Ingress Controller 是 Traefik，作为 DaemonSet 部署在 `traefik` 命名空间中。Pod 仅会调度到具有 `worker` 角色的节点。 检查 pod 是否运行在所有节点上： ``` -kubectl -n ingress-nginx get pods -o wide +kubectl -n traefik get pods -o wide ``` 输出示例： ``` -kubectl -n ingress-nginx get pods -o wide +kubectl -n traefik get pods -o wide NAME READY STATUS RESTARTS AGE IP NODE default-http-backend-797c5bc547-kwwlq 1/1 Running 0 17m x.x.x.x worker-1 -nginx-ingress-controller-4qd64 1/1 Running 0 14m x.x.x.x worker-1 -nginx-ingress-controller-8wxhm 1/1 Running 0 13m x.x.x.x worker-0 +traefik-4qd64 1/1 Running 0 14m x.x.x.x worker-1 +traefik-8wxhm 1/1 Running 0 13m x.x.x.x worker-0 ``` 如果 pod 无法运行（即状态不是 **Running**，Ready 状态未显示 `1/1`，或者有大量 Restarts），请检查 pod 详细信息，日志和命名空间事件。 @@ -97,27 +97,27 @@ nginx-ingress-controller-8wxhm 1/1 Running 0 13m ### Pod 详细信息 ``` -kubectl -n ingress-nginx describe pods -l app=ingress-nginx +kubectl -n traefik describe pods -l app=traefik ``` ### Pod 容器日志 -下面的命令可以显示所有标记为 “app=ingress-nginx” 的 pod 的日志，但是由于 `kubectl logs` 命令的限制，它只会显示 10 行日志。有关详细信息，请参阅 `kubectl logs -h` 的 `--tail`。 +下面的命令可以显示所有标记为 “app=traefik” 的 pod 的日志，但是由于 `kubectl logs` 命令的限制，它只会显示 10 行日志。有关详细信息，请参阅 `kubectl logs -h` 的 `--tail`。 ``` -kubectl -n ingress-nginx logs -l app=ingress-nginx +kubectl -n traefik logs -l app=traefik ``` 如果需要查看完整的日志，请在命令中尾随 pod 名称： ``` -kubectl -n ingress-nginx logs +kubectl -n traefik logs ``` ### 命名空间事件 ``` -kubectl -n ingress-nginx get events +kubectl -n traefik get events ``` ### 调试日志 @@ -125,7 +125,7 @@ kubectl -n ingress-nginx get events 要启用调试日志： ``` -kubectl -n ingress-nginx patch ds nginx-ingress-controller --type='json' -p='[{"op": "add", "path": "/spec/template/spec/containers/0/args/-", "value": "--v=5"}]' +kubectl -n traefik patch ds traefik --type='json' -p='[{"op": "add", "path": "/spec/template/spec/containers/0/args/-", "value": "--v=5"}]' ``` ### 检查配置 @@ -133,7 +133,7 @@ kubectl -n ingress-nginx patch ds nginx-ingress-controller --type='json' -p='[{" 在每个 pod 中检索生成的配置： ``` -kubectl -n ingress-nginx get pods -l app=ingress-nginx --no-headers -o custom-columns=.NAME:.metadata.name | while read pod; do kubectl -n ingress-nginx exec $pod -- cat /etc/nginx/nginx.conf; done +kubectl -n traefik get pods -l app=traefik --no-headers -o custom-columns=.NAME:.metadata.name | while read pod; do kubectl -n traefik exec $pod -- cat /etc/nginx/nginx.conf; done ``` ## Rancher Agents diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.13/troubleshooting/other-troubleshooting-tips/kubernetes-resources.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.13/troubleshooting/other-troubleshooting-tips/kubernetes-resources.md index 6fee94b2cb4..db4b79ae3d8 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/version-2.13/troubleshooting/other-troubleshooting-tips/kubernetes-resources.md +++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.13/troubleshooting/other-troubleshooting-tips/kubernetes-resources.md @@ -74,22 +74,22 @@ kubectl -n kube-system get endpoints kube-scheduler -o jsonpath='{.metadata.anno ## Ingress Controller -默认的 Ingress Controller 是 NGINX，作为 DaemonSet 部署在 `ingress-nginx` 命名空间中。Pod 仅会调度到具有 `worker` 角色的节点。 +默认的 Ingress Controller 是 Traefik，作为 DaemonSet 部署在 `traefik` 命名空间中。Pod 仅会调度到具有 `worker` 角色的节点。 检查 pod 是否运行在所有节点上： ``` -kubectl -n ingress-nginx get pods -o wide +kubectl -n traefik get pods -o wide ``` 输出示例： ``` -kubectl -n ingress-nginx get pods -o wide +kubectl -n traefik get pods -o wide NAME READY STATUS RESTARTS AGE IP NODE default-http-backend-797c5bc547-kwwlq 1/1 Running 0 17m x.x.x.x worker-1 -nginx-ingress-controller-4qd64 1/1 Running 0 14m x.x.x.x worker-1 -nginx-ingress-controller-8wxhm 1/1 Running 0 13m x.x.x.x worker-0 +traefik-4qd64 1/1 Running 0 14m x.x.x.x worker-1 +traefik-8wxhm 1/1 Running 0 13m x.x.x.x worker-0 ``` 如果 pod 无法运行（即状态不是 **Running**，Ready 状态未显示 `1/1`，或者有大量 Restarts），请检查 pod 详细信息，日志和命名空间事件。 @@ -97,27 +97,27 @@ nginx-ingress-controller-8wxhm 1/1 Running 0 13m ### Pod 详细信息 ``` -kubectl -n ingress-nginx describe pods -l app=ingress-nginx +kubectl -n traefik describe pods -l app=traefik ``` ### Pod 容器日志 -下面的命令可以显示所有标记为 “app=ingress-nginx” 的 pod 的日志，但是由于 `kubectl logs` 命令的限制，它只会显示 10 行日志。有关详细信息，请参阅 `kubectl logs -h` 的 `--tail`。 +下面的命令可以显示所有标记为 “app=traefik” 的 pod 的日志，但是由于 `kubectl logs` 命令的限制，它只会显示 10 行日志。有关详细信息，请参阅 `kubectl logs -h` 的 `--tail`。 ``` -kubectl -n ingress-nginx logs -l app=ingress-nginx +kubectl -n traefik logs -l app=traefik ``` 如果需要查看完整的日志，请在命令中尾随 pod 名称： ``` -kubectl -n ingress-nginx logs +kubectl -n traefik logs ``` ### 命名空间事件 ``` -kubectl -n ingress-nginx get events +kubectl -n traefik get events ``` ### 调试日志 @@ -125,7 +125,7 @@ kubectl -n ingress-nginx get events 要启用调试日志： ``` -kubectl -n ingress-nginx patch ds nginx-ingress-controller --type='json' -p='[{"op": "add", "path": "/spec/template/spec/containers/0/args/-", "value": "--v=5"}]' +kubectl -n traefik patch ds traefik --type='json' -p='[{"op": "add", "path": "/spec/template/spec/containers/0/args/-", "value": "--v=5"}]' ``` ### 检查配置 @@ -133,7 +133,7 @@ kubectl -n ingress-nginx patch ds nginx-ingress-controller --type='json' -p='[{" 在每个 pod 中检索生成的配置： ``` -kubectl -n ingress-nginx get pods -l app=ingress-nginx --no-headers -o custom-columns=.NAME:.metadata.name | while read pod; do kubectl -n ingress-nginx exec $pod -- cat /etc/nginx/nginx.conf; done +kubectl -n traefik get pods -l app=traefik --no-headers -o custom-columns=.NAME:.metadata.name | while read pod; do kubectl -n traefik exec $pod -- cat /etc/nginx/nginx.conf; done ``` ## Rancher Agents diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.14/troubleshooting/other-troubleshooting-tips/kubernetes-resources.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.14/troubleshooting/other-troubleshooting-tips/kubernetes-resources.md index 6fee94b2cb4..db4b79ae3d8 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/version-2.14/troubleshooting/other-troubleshooting-tips/kubernetes-resources.md +++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.14/troubleshooting/other-troubleshooting-tips/kubernetes-resources.md @@ -74,22 +74,22 @@ kubectl -n kube-system get endpoints kube-scheduler -o jsonpath='{.metadata.anno ## Ingress Controller -默认的 Ingress Controller 是 NGINX，作为 DaemonSet 部署在 `ingress-nginx` 命名空间中。Pod 仅会调度到具有 `worker` 角色的节点。 +默认的 Ingress Controller 是 Traefik，作为 DaemonSet 部署在 `traefik` 命名空间中。Pod 仅会调度到具有 `worker` 角色的节点。 检查 pod 是否运行在所有节点上： ``` -kubectl -n ingress-nginx get pods -o wide +kubectl -n traefik get pods -o wide ``` 输出示例： ``` -kubectl -n ingress-nginx get pods -o wide +kubectl -n traefik get pods -o wide NAME READY STATUS RESTARTS AGE IP NODE default-http-backend-797c5bc547-kwwlq 1/1 Running 0 17m x.x.x.x worker-1 -nginx-ingress-controller-4qd64 1/1 Running 0 14m x.x.x.x worker-1 -nginx-ingress-controller-8wxhm 1/1 Running 0 13m x.x.x.x worker-0 +traefik-4qd64 1/1 Running 0 14m x.x.x.x worker-1 +traefik-8wxhm 1/1 Running 0 13m x.x.x.x worker-0 ``` 如果 pod 无法运行（即状态不是 **Running**，Ready 状态未显示 `1/1`，或者有大量 Restarts），请检查 pod 详细信息，日志和命名空间事件。 @@ -97,27 +97,27 @@ nginx-ingress-controller-8wxhm 1/1 Running 0 13m ### Pod 详细信息 ``` -kubectl -n ingress-nginx describe pods -l app=ingress-nginx +kubectl -n traefik describe pods -l app=traefik ``` ### Pod 容器日志 -下面的命令可以显示所有标记为 “app=ingress-nginx” 的 pod 的日志，但是由于 `kubectl logs` 命令的限制，它只会显示 10 行日志。有关详细信息，请参阅 `kubectl logs -h` 的 `--tail`。 +下面的命令可以显示所有标记为 “app=traefik” 的 pod 的日志，但是由于 `kubectl logs` 命令的限制，它只会显示 10 行日志。有关详细信息，请参阅 `kubectl logs -h` 的 `--tail`。 ``` -kubectl -n ingress-nginx logs -l app=ingress-nginx +kubectl -n traefik logs -l app=traefik ``` 如果需要查看完整的日志，请在命令中尾随 pod 名称： ``` -kubectl -n ingress-nginx logs +kubectl -n traefik logs ``` ### 命名空间事件 ``` -kubectl -n ingress-nginx get events +kubectl -n traefik get events ``` ### 调试日志 @@ -125,7 +125,7 @@ kubectl -n ingress-nginx get events 要启用调试日志： ``` -kubectl -n ingress-nginx patch ds nginx-ingress-controller --type='json' -p='[{"op": "add", "path": "/spec/template/spec/containers/0/args/-", "value": "--v=5"}]' +kubectl -n traefik patch ds traefik --type='json' -p='[{"op": "add", "path": "/spec/template/spec/containers/0/args/-", "value": "--v=5"}]' ``` ### 检查配置 @@ -133,7 +133,7 @@ kubectl -n ingress-nginx patch ds nginx-ingress-controller --type='json' -p='[{" 在每个 pod 中检索生成的配置： ``` -kubectl -n ingress-nginx get pods -l app=ingress-nginx --no-headers -o custom-columns=.NAME:.metadata.name | while read pod; do kubectl -n ingress-nginx exec $pod -- cat /etc/nginx/nginx.conf; done +kubectl -n traefik get pods -l app=traefik --no-headers -o custom-columns=.NAME:.metadata.name | while read pod; do kubectl -n traefik exec $pod -- cat /etc/nginx/nginx.conf; done ``` ## Rancher Agents diff --git a/versioned_docs/version-2.10/troubleshooting/other-troubleshooting-tips/kubernetes-resources.md b/versioned_docs/version-2.10/troubleshooting/other-troubleshooting-tips/kubernetes-resources.md index 635e4d07371..c79927b39c2 100644 --- a/versioned_docs/version-2.10/troubleshooting/other-troubleshooting-tips/kubernetes-resources.md +++ b/versioned_docs/version-2.10/troubleshooting/other-troubleshooting-tips/kubernetes-resources.md @@ -78,22 +78,22 @@ kubectl -n kube-system get endpoints kube-scheduler -o jsonpath='{.metadata.anno ## Ingress Controller -The default Ingress Controller is NGINX and is deployed as a DaemonSet in the `ingress-nginx` namespace. The pods are only scheduled to nodes with the `worker` role. +The default Ingress Controller is Traefik and is deployed as a DaemonSet in the `traefik` namespace. The pods are only scheduled to nodes with the `worker` role. Check if the pods are running on all nodes: ``` -kubectl -n ingress-nginx get pods -o wide +kubectl -n traefik get pods -o wide ``` Example output: ``` -kubectl -n ingress-nginx get pods -o wide +kubectl -n traefik get pods -o wide NAME READY STATUS RESTARTS AGE IP NODE default-http-backend-797c5bc547-kwwlq 1/1 Running 0 17m x.x.x.x worker-1 -nginx-ingress-controller-4qd64 1/1 Running 0 14m x.x.x.x worker-1 -nginx-ingress-controller-8wxhm 1/1 Running 0 13m x.x.x.x worker-0 +traefik-4qd64 1/1 Running 0 14m x.x.x.x worker-1 +traefik-8wxhm 1/1 Running 0 13m x.x.x.x worker-0 ``` If a pod is unable to run (Status is not **Running**, Ready status is not showing `1/1` or you see a high count of Restarts), check the pod details, logs and namespace events. @@ -101,27 +101,27 @@ If a pod is unable to run (Status is not **Running**, Ready status is not showin ### Pod details ``` -kubectl -n ingress-nginx describe pods -l app=ingress-nginx +kubectl -n traefik describe pods -l app=traefik ``` ### Pod container logs -The below command can show the logs of all the pods labeled "app=ingress-nginx", but it will display only 10 lines of log because of the restrictions of the `kubectl logs` command. Refer to `--tail` of `kubectl logs -h` for more information. +The below command can show the logs of all the pods labeled "app=traefik", but it will display only 10 lines of log because of the restrictions of the `kubectl logs` command. Refer to `--tail` of `kubectl logs -h` for more information. ``` -kubectl -n ingress-nginx logs -l app=ingress-nginx +kubectl -n traefik logs -l app=traefik ``` If the full log is needed, specify the pod name in the trailing command: ``` -kubectl -n ingress-nginx logs +kubectl -n traefik logs ``` ### Namespace events ``` -kubectl -n ingress-nginx get events +kubectl -n traefik get events ``` ### Debug logging @@ -129,7 +129,7 @@ kubectl -n ingress-nginx get events To enable debug logging: ``` -kubectl -n ingress-nginx patch ds nginx-ingress-controller --type='json' -p='[{"op": "add", "path": "/spec/template/spec/containers/0/args/-", "value": "--v=5"}]' +kubectl -n traefik patch ds traefik --type='json' -p='[{"op": "add", "path": "/spec/template/spec/containers/0/args/-", "value": "--v=5"}]' ``` ### Check configuration @@ -137,7 +137,7 @@ kubectl -n ingress-nginx patch ds nginx-ingress-controller --type='json' -p='[{" Retrieve generated configuration in each pod: ``` -kubectl -n ingress-nginx get pods -l app=ingress-nginx --no-headers -o custom-columns=.NAME:.metadata.name | while read pod; do kubectl -n ingress-nginx exec $pod -- cat /etc/nginx/nginx.conf; done +kubectl -n traefik get pods -l app=traefik --no-headers -o custom-columns=.NAME:.metadata.name | while read pod; do kubectl -n traefik exec $pod -- cat /etc/nginx/nginx.conf; done ``` ## Rancher agents diff --git a/versioned_docs/version-2.11/troubleshooting/other-troubleshooting-tips/kubernetes-resources.md b/versioned_docs/version-2.11/troubleshooting/other-troubleshooting-tips/kubernetes-resources.md index 635e4d07371..c79927b39c2 100644 --- a/versioned_docs/version-2.11/troubleshooting/other-troubleshooting-tips/kubernetes-resources.md +++ b/versioned_docs/version-2.11/troubleshooting/other-troubleshooting-tips/kubernetes-resources.md @@ -78,22 +78,22 @@ kubectl -n kube-system get endpoints kube-scheduler -o jsonpath='{.metadata.anno ## Ingress Controller -The default Ingress Controller is NGINX and is deployed as a DaemonSet in the `ingress-nginx` namespace. The pods are only scheduled to nodes with the `worker` role. +The default Ingress Controller is Traefik and is deployed as a DaemonSet in the `traefik` namespace. The pods are only scheduled to nodes with the `worker` role. Check if the pods are running on all nodes: ``` -kubectl -n ingress-nginx get pods -o wide +kubectl -n traefik get pods -o wide ``` Example output: ``` -kubectl -n ingress-nginx get pods -o wide +kubectl -n traefik get pods -o wide NAME READY STATUS RESTARTS AGE IP NODE default-http-backend-797c5bc547-kwwlq 1/1 Running 0 17m x.x.x.x worker-1 -nginx-ingress-controller-4qd64 1/1 Running 0 14m x.x.x.x worker-1 -nginx-ingress-controller-8wxhm 1/1 Running 0 13m x.x.x.x worker-0 +traefik-4qd64 1/1 Running 0 14m x.x.x.x worker-1 +traefik-8wxhm 1/1 Running 0 13m x.x.x.x worker-0 ``` If a pod is unable to run (Status is not **Running**, Ready status is not showing `1/1` or you see a high count of Restarts), check the pod details, logs and namespace events. @@ -101,27 +101,27 @@ If a pod is unable to run (Status is not **Running**, Ready status is not showin ### Pod details ``` -kubectl -n ingress-nginx describe pods -l app=ingress-nginx +kubectl -n traefik describe pods -l app=traefik ``` ### Pod container logs -The below command can show the logs of all the pods labeled "app=ingress-nginx", but it will display only 10 lines of log because of the restrictions of the `kubectl logs` command. Refer to `--tail` of `kubectl logs -h` for more information. +The below command can show the logs of all the pods labeled "app=traefik", but it will display only 10 lines of log because of the restrictions of the `kubectl logs` command. Refer to `--tail` of `kubectl logs -h` for more information. ``` -kubectl -n ingress-nginx logs -l app=ingress-nginx +kubectl -n traefik logs -l app=traefik ``` If the full log is needed, specify the pod name in the trailing command: ``` -kubectl -n ingress-nginx logs +kubectl -n traefik logs ``` ### Namespace events ``` -kubectl -n ingress-nginx get events +kubectl -n traefik get events ``` ### Debug logging @@ -129,7 +129,7 @@ kubectl -n ingress-nginx get events To enable debug logging: ``` -kubectl -n ingress-nginx patch ds nginx-ingress-controller --type='json' -p='[{"op": "add", "path": "/spec/template/spec/containers/0/args/-", "value": "--v=5"}]' +kubectl -n traefik patch ds traefik --type='json' -p='[{"op": "add", "path": "/spec/template/spec/containers/0/args/-", "value": "--v=5"}]' ``` ### Check configuration @@ -137,7 +137,7 @@ kubectl -n ingress-nginx patch ds nginx-ingress-controller --type='json' -p='[{" Retrieve generated configuration in each pod: ``` -kubectl -n ingress-nginx get pods -l app=ingress-nginx --no-headers -o custom-columns=.NAME:.metadata.name | while read pod; do kubectl -n ingress-nginx exec $pod -- cat /etc/nginx/nginx.conf; done +kubectl -n traefik get pods -l app=traefik --no-headers -o custom-columns=.NAME:.metadata.name | while read pod; do kubectl -n traefik exec $pod -- cat /etc/nginx/nginx.conf; done ``` ## Rancher agents diff --git a/versioned_docs/version-2.12/troubleshooting/other-troubleshooting-tips/kubernetes-resources.md b/versioned_docs/version-2.12/troubleshooting/other-troubleshooting-tips/kubernetes-resources.md index 635e4d07371..c79927b39c2 100644 --- a/versioned_docs/version-2.12/troubleshooting/other-troubleshooting-tips/kubernetes-resources.md +++ b/versioned_docs/version-2.12/troubleshooting/other-troubleshooting-tips/kubernetes-resources.md @@ -78,22 +78,22 @@ kubectl -n kube-system get endpoints kube-scheduler -o jsonpath='{.metadata.anno ## Ingress Controller -The default Ingress Controller is NGINX and is deployed as a DaemonSet in the `ingress-nginx` namespace. The pods are only scheduled to nodes with the `worker` role. +The default Ingress Controller is Traefik and is deployed as a DaemonSet in the `traefik` namespace. The pods are only scheduled to nodes with the `worker` role. Check if the pods are running on all nodes: ``` -kubectl -n ingress-nginx get pods -o wide +kubectl -n traefik get pods -o wide ``` Example output: ``` -kubectl -n ingress-nginx get pods -o wide +kubectl -n traefik get pods -o wide NAME READY STATUS RESTARTS AGE IP NODE default-http-backend-797c5bc547-kwwlq 1/1 Running 0 17m x.x.x.x worker-1 -nginx-ingress-controller-4qd64 1/1 Running 0 14m x.x.x.x worker-1 -nginx-ingress-controller-8wxhm 1/1 Running 0 13m x.x.x.x worker-0 +traefik-4qd64 1/1 Running 0 14m x.x.x.x worker-1 +traefik-8wxhm 1/1 Running 0 13m x.x.x.x worker-0 ``` If a pod is unable to run (Status is not **Running**, Ready status is not showing `1/1` or you see a high count of Restarts), check the pod details, logs and namespace events. @@ -101,27 +101,27 @@ If a pod is unable to run (Status is not **Running**, Ready status is not showin ### Pod details ``` -kubectl -n ingress-nginx describe pods -l app=ingress-nginx +kubectl -n traefik describe pods -l app=traefik ``` ### Pod container logs -The below command can show the logs of all the pods labeled "app=ingress-nginx", but it will display only 10 lines of log because of the restrictions of the `kubectl logs` command. Refer to `--tail` of `kubectl logs -h` for more information. +The below command can show the logs of all the pods labeled "app=traefik", but it will display only 10 lines of log because of the restrictions of the `kubectl logs` command. Refer to `--tail` of `kubectl logs -h` for more information. ``` -kubectl -n ingress-nginx logs -l app=ingress-nginx +kubectl -n traefik logs -l app=traefik ``` If the full log is needed, specify the pod name in the trailing command: ``` -kubectl -n ingress-nginx logs +kubectl -n traefik logs ``` ### Namespace events ``` -kubectl -n ingress-nginx get events +kubectl -n traefik get events ``` ### Debug logging @@ -129,7 +129,7 @@ kubectl -n ingress-nginx get events To enable debug logging: ``` -kubectl -n ingress-nginx patch ds nginx-ingress-controller --type='json' -p='[{"op": "add", "path": "/spec/template/spec/containers/0/args/-", "value": "--v=5"}]' +kubectl -n traefik patch ds traefik --type='json' -p='[{"op": "add", "path": "/spec/template/spec/containers/0/args/-", "value": "--v=5"}]' ``` ### Check configuration @@ -137,7 +137,7 @@ kubectl -n ingress-nginx patch ds nginx-ingress-controller --type='json' -p='[{" Retrieve generated configuration in each pod: ``` -kubectl -n ingress-nginx get pods -l app=ingress-nginx --no-headers -o custom-columns=.NAME:.metadata.name | while read pod; do kubectl -n ingress-nginx exec $pod -- cat /etc/nginx/nginx.conf; done +kubectl -n traefik get pods -l app=traefik --no-headers -o custom-columns=.NAME:.metadata.name | while read pod; do kubectl -n traefik exec $pod -- cat /etc/nginx/nginx.conf; done ``` ## Rancher agents diff --git a/versioned_docs/version-2.13/troubleshooting/other-troubleshooting-tips/kubernetes-resources.md b/versioned_docs/version-2.13/troubleshooting/other-troubleshooting-tips/kubernetes-resources.md index 635e4d07371..c79927b39c2 100644 --- a/versioned_docs/version-2.13/troubleshooting/other-troubleshooting-tips/kubernetes-resources.md +++ b/versioned_docs/version-2.13/troubleshooting/other-troubleshooting-tips/kubernetes-resources.md @@ -78,22 +78,22 @@ kubectl -n kube-system get endpoints kube-scheduler -o jsonpath='{.metadata.anno ## Ingress Controller -The default Ingress Controller is NGINX and is deployed as a DaemonSet in the `ingress-nginx` namespace. The pods are only scheduled to nodes with the `worker` role. +The default Ingress Controller is Traefik and is deployed as a DaemonSet in the `traefik` namespace. The pods are only scheduled to nodes with the `worker` role. Check if the pods are running on all nodes: ``` -kubectl -n ingress-nginx get pods -o wide +kubectl -n traefik get pods -o wide ``` Example output: ``` -kubectl -n ingress-nginx get pods -o wide +kubectl -n traefik get pods -o wide NAME READY STATUS RESTARTS AGE IP NODE default-http-backend-797c5bc547-kwwlq 1/1 Running 0 17m x.x.x.x worker-1 -nginx-ingress-controller-4qd64 1/1 Running 0 14m x.x.x.x worker-1 -nginx-ingress-controller-8wxhm 1/1 Running 0 13m x.x.x.x worker-0 +traefik-4qd64 1/1 Running 0 14m x.x.x.x worker-1 +traefik-8wxhm 1/1 Running 0 13m x.x.x.x worker-0 ``` If a pod is unable to run (Status is not **Running**, Ready status is not showing `1/1` or you see a high count of Restarts), check the pod details, logs and namespace events. @@ -101,27 +101,27 @@ If a pod is unable to run (Status is not **Running**, Ready status is not showin ### Pod details ``` -kubectl -n ingress-nginx describe pods -l app=ingress-nginx +kubectl -n traefik describe pods -l app=traefik ``` ### Pod container logs -The below command can show the logs of all the pods labeled "app=ingress-nginx", but it will display only 10 lines of log because of the restrictions of the `kubectl logs` command. Refer to `--tail` of `kubectl logs -h` for more information. +The below command can show the logs of all the pods labeled "app=traefik", but it will display only 10 lines of log because of the restrictions of the `kubectl logs` command. Refer to `--tail` of `kubectl logs -h` for more information. ``` -kubectl -n ingress-nginx logs -l app=ingress-nginx +kubectl -n traefik logs -l app=traefik ``` If the full log is needed, specify the pod name in the trailing command: ``` -kubectl -n ingress-nginx logs +kubectl -n traefik logs ``` ### Namespace events ``` -kubectl -n ingress-nginx get events +kubectl -n traefik get events ``` ### Debug logging @@ -129,7 +129,7 @@ kubectl -n ingress-nginx get events To enable debug logging: ``` -kubectl -n ingress-nginx patch ds nginx-ingress-controller --type='json' -p='[{"op": "add", "path": "/spec/template/spec/containers/0/args/-", "value": "--v=5"}]' +kubectl -n traefik patch ds traefik --type='json' -p='[{"op": "add", "path": "/spec/template/spec/containers/0/args/-", "value": "--v=5"}]' ``` ### Check configuration @@ -137,7 +137,7 @@ kubectl -n ingress-nginx patch ds nginx-ingress-controller --type='json' -p='[{" Retrieve generated configuration in each pod: ``` -kubectl -n ingress-nginx get pods -l app=ingress-nginx --no-headers -o custom-columns=.NAME:.metadata.name | while read pod; do kubectl -n ingress-nginx exec $pod -- cat /etc/nginx/nginx.conf; done +kubectl -n traefik get pods -l app=traefik --no-headers -o custom-columns=.NAME:.metadata.name | while read pod; do kubectl -n traefik exec $pod -- cat /etc/nginx/nginx.conf; done ``` ## Rancher agents diff --git a/versioned_docs/version-2.14/troubleshooting/other-troubleshooting-tips/kubernetes-resources.md b/versioned_docs/version-2.14/troubleshooting/other-troubleshooting-tips/kubernetes-resources.md index 635e4d07371..c79927b39c2 100644 --- a/versioned_docs/version-2.14/troubleshooting/other-troubleshooting-tips/kubernetes-resources.md +++ b/versioned_docs/version-2.14/troubleshooting/other-troubleshooting-tips/kubernetes-resources.md @@ -78,22 +78,22 @@ kubectl -n kube-system get endpoints kube-scheduler -o jsonpath='{.metadata.anno ## Ingress Controller -The default Ingress Controller is NGINX and is deployed as a DaemonSet in the `ingress-nginx` namespace. The pods are only scheduled to nodes with the `worker` role. +The default Ingress Controller is Traefik and is deployed as a DaemonSet in the `traefik` namespace. The pods are only scheduled to nodes with the `worker` role. Check if the pods are running on all nodes: ``` -kubectl -n ingress-nginx get pods -o wide +kubectl -n traefik get pods -o wide ``` Example output: ``` -kubectl -n ingress-nginx get pods -o wide +kubectl -n traefik get pods -o wide NAME READY STATUS RESTARTS AGE IP NODE default-http-backend-797c5bc547-kwwlq 1/1 Running 0 17m x.x.x.x worker-1 -nginx-ingress-controller-4qd64 1/1 Running 0 14m x.x.x.x worker-1 -nginx-ingress-controller-8wxhm 1/1 Running 0 13m x.x.x.x worker-0 +traefik-4qd64 1/1 Running 0 14m x.x.x.x worker-1 +traefik-8wxhm 1/1 Running 0 13m x.x.x.x worker-0 ``` If a pod is unable to run (Status is not **Running**, Ready status is not showing `1/1` or you see a high count of Restarts), check the pod details, logs and namespace events. @@ -101,27 +101,27 @@ If a pod is unable to run (Status is not **Running**, Ready status is not showin ### Pod details ``` -kubectl -n ingress-nginx describe pods -l app=ingress-nginx +kubectl -n traefik describe pods -l app=traefik ``` ### Pod container logs -The below command can show the logs of all the pods labeled "app=ingress-nginx", but it will display only 10 lines of log because of the restrictions of the `kubectl logs` command. Refer to `--tail` of `kubectl logs -h` for more information. +The below command can show the logs of all the pods labeled "app=traefik", but it will display only 10 lines of log because of the restrictions of the `kubectl logs` command. Refer to `--tail` of `kubectl logs -h` for more information. ``` -kubectl -n ingress-nginx logs -l app=ingress-nginx +kubectl -n traefik logs -l app=traefik ``` If the full log is needed, specify the pod name in the trailing command: ``` -kubectl -n ingress-nginx logs +kubectl -n traefik logs ``` ### Namespace events ``` -kubectl -n ingress-nginx get events +kubectl -n traefik get events ``` ### Debug logging @@ -129,7 +129,7 @@ kubectl -n ingress-nginx get events To enable debug logging: ``` -kubectl -n ingress-nginx patch ds nginx-ingress-controller --type='json' -p='[{"op": "add", "path": "/spec/template/spec/containers/0/args/-", "value": "--v=5"}]' +kubectl -n traefik patch ds traefik --type='json' -p='[{"op": "add", "path": "/spec/template/spec/containers/0/args/-", "value": "--v=5"}]' ``` ### Check configuration @@ -137,7 +137,7 @@ kubectl -n ingress-nginx patch ds nginx-ingress-controller --type='json' -p='[{" Retrieve generated configuration in each pod: ``` -kubectl -n ingress-nginx get pods -l app=ingress-nginx --no-headers -o custom-columns=.NAME:.metadata.name | while read pod; do kubectl -n ingress-nginx exec $pod -- cat /etc/nginx/nginx.conf; done +kubectl -n traefik get pods -l app=traefik --no-headers -o custom-columns=.NAME:.metadata.name | while read pod; do kubectl -n traefik exec $pod -- cat /etc/nginx/nginx.conf; done ``` ## Rancher agents