From eef73d106dbb9490f9e1a14fc6eec3d8a39c48e3 Mon Sep 17 00:00:00 2001 From: Sunil Singh Date: Tue, 17 Mar 2026 16:28:53 -0700 Subject: [PATCH] Reverting changes to troubleshooting.md as handled in related PR. Signed-off-by: Sunil Singh --- .../troubleshooting.md | 12 +++++++----- .../troubleshooting.md | 12 +++++++----- .../troubleshooting.md | 12 +++++++----- .../troubleshooting.md | 12 +++++++----- .../troubleshooting.md | 12 +++++++----- .../troubleshooting.md | 12 +++++++----- .../troubleshooting.md | 12 +++++++----- .../troubleshooting.md | 12 +++++++----- .../troubleshooting.md | 12 +++++++----- .../troubleshooting.md | 12 +++++++----- .../troubleshooting.md | 12 +++++++----- .../troubleshooting.md | 12 +++++++----- 12 files changed, 84 insertions(+), 60 deletions(-) diff --git a/docs/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/troubleshooting.md b/docs/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/troubleshooting.md index b35276f8c5a..881a6d871a0 100644 --- a/docs/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/troubleshooting.md +++ b/docs/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/troubleshooting.md @@ -13,7 +13,7 @@ This section describes how to troubleshoot an installation of Rancher on a Kuber Most of the troubleshooting will be done on objects in these 3 namespaces. - `cattle-system` - `rancher` deployment and pods. -- `traefik` - Ingress controller pods and services. +- `ingress-nginx` - Ingress controller pods and services. - `cert-manager` - `cert-manager` pods. ### "default backend - 404" @@ -115,7 +115,7 @@ Events: Your certs get applied directly to the Ingress object in the `cattle-system` namespace. -Check the status of the Ingress object and see if it's ready. +Check the status of the Ingress object and see if its ready. ``` kubectl -n cattle-system describe ingress @@ -123,10 +123,12 @@ kubectl -n cattle-system describe ingress If its ready and the SSL is still not working you may have a malformed cert or secret. -Check the `traefik` logs. +Check the nginx-ingress-controller logs. Because the nginx-ingress-controller has multiple containers in its pod you will need to specify the name of the container. ``` -kubectl -n traefik logs +kubectl -n ingress-nginx logs -f nginx-ingress-controller-rfjrq nginx-ingress-controller +... +W0705 23:04:58.240571 7 backend_ssl.go:49] error obtaining PEM from secret cattle-system/tls-rancher-ingress: error retrieving secret cattle-system/tls-rancher-ingress: secret cattle-system/tls-rancher-ingress was not found ``` ### No matches for kind "Issuer" @@ -146,7 +148,7 @@ The most common cause of this issue is port 8472/UDP is not open between the nod Once the network issue is resolved, the `canal` pods should timeout and restart to establish their connections. -### Traefik Pods show RESTARTS +### nginx-ingress-controller Pods show RESTARTS The most common cause of this issue is the `canal` pods have failed to establish the overlay network. See [canal Pods show READY `2/3`](#canal-pods-show-ready-23) for troubleshooting. diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/troubleshooting.md b/i18n/zh/docusaurus-plugin-content-docs/current/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/troubleshooting.md index 172c342d867..9a391416f4b 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/current/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/troubleshooting.md +++ b/i18n/zh/docusaurus-plugin-content-docs/current/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/troubleshooting.md @@ -9,7 +9,7 @@ title: Rancher Server Kubernetes 集群的问题排查 故障排除主要针对以下 3 个命名空间中的对象： - `cattle-system`：`rancher` deployment 和 Pod。 -- `traefik`：Ingress Controller Pod 和 services。 +- `ingress-nginx`：Ingress Controller Pod 和 services。 - `cert-manager`：`cert-manager` Pod。 ## "default backend - 404" @@ -117,12 +117,14 @@ Events: kubectl -n cattle-system describe ingress ``` -If its ready and the SSL is still not working you may have a malformed cert or secret. +如果 Ingress 对象已就绪，但是 SSL 仍然无法正常工作，你的证书或密文的格式可能不正确。 -Check the `traefik` logs. +这种情况下，请检查 nginx-ingress-controller 的日志。nginx-ingress-controller 的 Pod 中有多个容器，因此你需要指定容器的名称： ``` -kubectl -n traefik logs +kubectl -n ingress-nginx logs -f nginx-ingress-controller-rfjrq nginx-ingress-controller +... +W0705 23:04:58.240571 7 backend_ssl.go:49] error obtaining PEM from secret cattle-system/tls-rancher-ingress: error retrieving secret cattle-system/tls-rancher-ingress: secret cattle-system/tls-rancher-ingress was not found ``` ## 没有匹配的 "Issuer" @@ -142,7 +144,7 @@ Error: validation failed: unable to recognize "": no matches for kind "Issuer" i 解决网络问题后，`canal` Pod 会超时并重启以建立连接。 -## Traefik Pod 显示 RESTARTS +## nginx-ingress-controller Pod 显示 RESTARTS 此问题的最常见原因是 `canal` pod 未能建立覆盖网络。参见 [canal Pod 显示 READY `2/3`](#canal-pod-显示-ready-23) 进行排查。 diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.10/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/troubleshooting.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.10/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/troubleshooting.md index e1af566af0d..b303fc0c1c9 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/version-2.10/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/troubleshooting.md +++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.10/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/troubleshooting.md @@ -9,7 +9,7 @@ title: Rancher Server Kubernetes 集群的问题排查 故障排除主要针对以下 3 个命名空间中的对象： - `cattle-system`：`rancher` deployment 和 Pod。 -- `traaefik`：Ingress Controller Pod 和 services。 +- `ingress-nginx`：Ingress Controller Pod 和 services。 - `cert-manager`：`cert-manager` Pod。 ## "default backend - 404" @@ -117,12 +117,14 @@ Events: kubectl -n cattle-system describe ingress ``` -If its ready and the SSL is still not working you may have a malformed cert or secret. +如果 Ingress 对象已就绪，但是 SSL 仍然无法正常工作，你的证书或密文的格式可能不正确。 -Check the `traefik` logs. +这种情况下，请检查 nginx-ingress-controller 的日志。nginx-ingress-controller 的 Pod 中有多个容器，因此你需要指定容器的名称： ``` -kubectl -n traefik logs +kubectl -n ingress-nginx logs -f nginx-ingress-controller-rfjrq nginx-ingress-controller +... +W0705 23:04:58.240571 7 backend_ssl.go:49] error obtaining PEM from secret cattle-system/tls-rancher-ingress: error retrieving secret cattle-system/tls-rancher-ingress: secret cattle-system/tls-rancher-ingress was not found ``` ## 没有匹配的 "Issuer" @@ -142,7 +144,7 @@ Error: validation failed: unable to recognize "": no matches for kind "Issuer" i 解决网络问题后，`canal` Pod 会超时并重启以建立连接。 -## Traefik Pod 显示 RESTARTS +## nginx-ingress-controller Pod 显示 RESTARTS 此问题的最常见原因是 `canal` pod 未能建立覆盖网络。参见 [canal Pod 显示 READY `2/3`](#canal-pod-显示-ready-23) 进行排查。 diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.11/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/troubleshooting.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.11/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/troubleshooting.md index 140bfcda36a..b303fc0c1c9 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/version-2.11/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/troubleshooting.md +++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.11/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/troubleshooting.md @@ -9,7 +9,7 @@ title: Rancher Server Kubernetes 集群的问题排查 故障排除主要针对以下 3 个命名空间中的对象： - `cattle-system`：`rancher` deployment 和 Pod。 -- `traefik`：Ingress Controller Pod 和 services。 +- `ingress-nginx`：Ingress Controller Pod 和 services。 - `cert-manager`：`cert-manager` Pod。 ## "default backend - 404" @@ -117,12 +117,14 @@ Events: kubectl -n cattle-system describe ingress ``` -If its ready and the SSL is still not working you may have a malformed cert or secret. +如果 Ingress 对象已就绪，但是 SSL 仍然无法正常工作，你的证书或密文的格式可能不正确。 -Check the `traefik` logs. +这种情况下，请检查 nginx-ingress-controller 的日志。nginx-ingress-controller 的 Pod 中有多个容器，因此你需要指定容器的名称： ``` -kubectl -n traefik logs +kubectl -n ingress-nginx logs -f nginx-ingress-controller-rfjrq nginx-ingress-controller +... +W0705 23:04:58.240571 7 backend_ssl.go:49] error obtaining PEM from secret cattle-system/tls-rancher-ingress: error retrieving secret cattle-system/tls-rancher-ingress: secret cattle-system/tls-rancher-ingress was not found ``` ## 没有匹配的 "Issuer" @@ -142,7 +144,7 @@ Error: validation failed: unable to recognize "": no matches for kind "Issuer" i 解决网络问题后，`canal` Pod 会超时并重启以建立连接。 -## Traefik Pod 显示 RESTARTS +## nginx-ingress-controller Pod 显示 RESTARTS 此问题的最常见原因是 `canal` pod 未能建立覆盖网络。参见 [canal Pod 显示 READY `2/3`](#canal-pod-显示-ready-23) 进行排查。 diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.12/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/troubleshooting.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.12/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/troubleshooting.md index 172c342d867..9a391416f4b 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/version-2.12/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/troubleshooting.md +++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.12/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/troubleshooting.md @@ -9,7 +9,7 @@ title: Rancher Server Kubernetes 集群的问题排查 故障排除主要针对以下 3 个命名空间中的对象： - `cattle-system`：`rancher` deployment 和 Pod。 -- `traefik`：Ingress Controller Pod 和 services。 +- `ingress-nginx`：Ingress Controller Pod 和 services。 - `cert-manager`：`cert-manager` Pod。 ## "default backend - 404" @@ -117,12 +117,14 @@ Events: kubectl -n cattle-system describe ingress ``` -If its ready and the SSL is still not working you may have a malformed cert or secret. +如果 Ingress 对象已就绪，但是 SSL 仍然无法正常工作，你的证书或密文的格式可能不正确。 -Check the `traefik` logs. +这种情况下，请检查 nginx-ingress-controller 的日志。nginx-ingress-controller 的 Pod 中有多个容器，因此你需要指定容器的名称： ``` -kubectl -n traefik logs +kubectl -n ingress-nginx logs -f nginx-ingress-controller-rfjrq nginx-ingress-controller +... +W0705 23:04:58.240571 7 backend_ssl.go:49] error obtaining PEM from secret cattle-system/tls-rancher-ingress: error retrieving secret cattle-system/tls-rancher-ingress: secret cattle-system/tls-rancher-ingress was not found ``` ## 没有匹配的 "Issuer" @@ -142,7 +144,7 @@ Error: validation failed: unable to recognize "": no matches for kind "Issuer" i 解决网络问题后，`canal` Pod 会超时并重启以建立连接。 -## Traefik Pod 显示 RESTARTS +## nginx-ingress-controller Pod 显示 RESTARTS 此问题的最常见原因是 `canal` pod 未能建立覆盖网络。参见 [canal Pod 显示 READY `2/3`](#canal-pod-显示-ready-23) 进行排查。 diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.13/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/troubleshooting.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.13/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/troubleshooting.md index 172c342d867..9a391416f4b 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/version-2.13/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/troubleshooting.md +++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.13/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/troubleshooting.md @@ -9,7 +9,7 @@ title: Rancher Server Kubernetes 集群的问题排查 故障排除主要针对以下 3 个命名空间中的对象： - `cattle-system`：`rancher` deployment 和 Pod。 -- `traefik`：Ingress Controller Pod 和 services。 +- `ingress-nginx`：Ingress Controller Pod 和 services。 - `cert-manager`：`cert-manager` Pod。 ## "default backend - 404" @@ -117,12 +117,14 @@ Events: kubectl -n cattle-system describe ingress ``` -If its ready and the SSL is still not working you may have a malformed cert or secret. +如果 Ingress 对象已就绪，但是 SSL 仍然无法正常工作，你的证书或密文的格式可能不正确。 -Check the `traefik` logs. +这种情况下，请检查 nginx-ingress-controller 的日志。nginx-ingress-controller 的 Pod 中有多个容器，因此你需要指定容器的名称： ``` -kubectl -n traefik logs +kubectl -n ingress-nginx logs -f nginx-ingress-controller-rfjrq nginx-ingress-controller +... +W0705 23:04:58.240571 7 backend_ssl.go:49] error obtaining PEM from secret cattle-system/tls-rancher-ingress: error retrieving secret cattle-system/tls-rancher-ingress: secret cattle-system/tls-rancher-ingress was not found ``` ## 没有匹配的 "Issuer" @@ -142,7 +144,7 @@ Error: validation failed: unable to recognize "": no matches for kind "Issuer" i 解决网络问题后，`canal` Pod 会超时并重启以建立连接。 -## Traefik Pod 显示 RESTARTS +## nginx-ingress-controller Pod 显示 RESTARTS 此问题的最常见原因是 `canal` pod 未能建立覆盖网络。参见 [canal Pod 显示 READY `2/3`](#canal-pod-显示-ready-23) 进行排查。 diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.14/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/troubleshooting.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.14/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/troubleshooting.md index 172c342d867..9a391416f4b 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/version-2.14/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/troubleshooting.md +++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.14/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/troubleshooting.md @@ -9,7 +9,7 @@ title: Rancher Server Kubernetes 集群的问题排查 故障排除主要针对以下 3 个命名空间中的对象： - `cattle-system`：`rancher` deployment 和 Pod。 -- `traefik`：Ingress Controller Pod 和 services。 +- `ingress-nginx`：Ingress Controller Pod 和 services。 - `cert-manager`：`cert-manager` Pod。 ## "default backend - 404" @@ -117,12 +117,14 @@ Events: kubectl -n cattle-system describe ingress ``` -If its ready and the SSL is still not working you may have a malformed cert or secret. +如果 Ingress 对象已就绪，但是 SSL 仍然无法正常工作，你的证书或密文的格式可能不正确。 -Check the `traefik` logs. +这种情况下，请检查 nginx-ingress-controller 的日志。nginx-ingress-controller 的 Pod 中有多个容器，因此你需要指定容器的名称： ``` -kubectl -n traefik logs +kubectl -n ingress-nginx logs -f nginx-ingress-controller-rfjrq nginx-ingress-controller +... +W0705 23:04:58.240571 7 backend_ssl.go:49] error obtaining PEM from secret cattle-system/tls-rancher-ingress: error retrieving secret cattle-system/tls-rancher-ingress: secret cattle-system/tls-rancher-ingress was not found ``` ## 没有匹配的 "Issuer" @@ -142,7 +144,7 @@ Error: validation failed: unable to recognize "": no matches for kind "Issuer" i 解决网络问题后，`canal` Pod 会超时并重启以建立连接。 -## Traefik Pod 显示 RESTARTS +## nginx-ingress-controller Pod 显示 RESTARTS 此问题的最常见原因是 `canal` pod 未能建立覆盖网络。参见 [canal Pod 显示 READY `2/3`](#canal-pod-显示-ready-23) 进行排查。 diff --git a/versioned_docs/version-2.10/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/troubleshooting.md b/versioned_docs/version-2.10/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/troubleshooting.md index e3b73292da3..4fa1f09c8f6 100644 --- a/versioned_docs/version-2.10/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/troubleshooting.md +++ b/versioned_docs/version-2.10/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/troubleshooting.md @@ -13,7 +13,7 @@ This section describes how to troubleshoot an installation of Rancher on a Kuber Most of the troubleshooting will be done on objects in these 3 namespaces. - `cattle-system` - `rancher` deployment and pods. -- `traefik` - Ingress controller pods and services. +- `ingress-nginx` - Ingress controller pods and services. - `cert-manager` - `cert-manager` pods. ### "default backend - 404" @@ -115,7 +115,7 @@ Events: Your certs get applied directly to the Ingress object in the `cattle-system` namespace. -Check the status of the Ingress object and see if it's ready. +Check the status of the Ingress object and see if its ready. ``` kubectl -n cattle-system describe ingress @@ -123,10 +123,12 @@ kubectl -n cattle-system describe ingress If its ready and the SSL is still not working you may have a malformed cert or secret. -Check the `traefik` logs. +Check the nginx-ingress-controller logs. Because the nginx-ingress-controller has multiple containers in its pod you will need to specify the name of the container. ``` -kubectl -n traefik logs +kubectl -n ingress-nginx logs -f nginx-ingress-controller-rfjrq nginx-ingress-controller +... +W0705 23:04:58.240571 7 backend_ssl.go:49] error obtaining PEM from secret cattle-system/tls-rancher-ingress: error retrieving secret cattle-system/tls-rancher-ingress: secret cattle-system/tls-rancher-ingress was not found ``` ### No matches for kind "Issuer" @@ -146,7 +148,7 @@ The most common cause of this issue is port 8472/UDP is not open between the nod Once the network issue is resolved, the `canal` pods should timeout and restart to establish their connections. -### Traefik Pods show RESTARTS +### nginx-ingress-controller Pods show RESTARTS The most common cause of this issue is the `canal` pods have failed to establish the overlay network. See [canal Pods show READY `2/3`](#canal-pods-show-ready-23) for troubleshooting. diff --git a/versioned_docs/version-2.11/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/troubleshooting.md b/versioned_docs/version-2.11/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/troubleshooting.md index e3b73292da3..4fa1f09c8f6 100644 --- a/versioned_docs/version-2.11/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/troubleshooting.md +++ b/versioned_docs/version-2.11/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/troubleshooting.md @@ -13,7 +13,7 @@ This section describes how to troubleshoot an installation of Rancher on a Kuber Most of the troubleshooting will be done on objects in these 3 namespaces. - `cattle-system` - `rancher` deployment and pods. -- `traefik` - Ingress controller pods and services. +- `ingress-nginx` - Ingress controller pods and services. - `cert-manager` - `cert-manager` pods. ### "default backend - 404" @@ -115,7 +115,7 @@ Events: Your certs get applied directly to the Ingress object in the `cattle-system` namespace. -Check the status of the Ingress object and see if it's ready. +Check the status of the Ingress object and see if its ready. ``` kubectl -n cattle-system describe ingress @@ -123,10 +123,12 @@ kubectl -n cattle-system describe ingress If its ready and the SSL is still not working you may have a malformed cert or secret. -Check the `traefik` logs. +Check the nginx-ingress-controller logs. Because the nginx-ingress-controller has multiple containers in its pod you will need to specify the name of the container. ``` -kubectl -n traefik logs +kubectl -n ingress-nginx logs -f nginx-ingress-controller-rfjrq nginx-ingress-controller +... +W0705 23:04:58.240571 7 backend_ssl.go:49] error obtaining PEM from secret cattle-system/tls-rancher-ingress: error retrieving secret cattle-system/tls-rancher-ingress: secret cattle-system/tls-rancher-ingress was not found ``` ### No matches for kind "Issuer" @@ -146,7 +148,7 @@ The most common cause of this issue is port 8472/UDP is not open between the nod Once the network issue is resolved, the `canal` pods should timeout and restart to establish their connections. -### Traefik Pods show RESTARTS +### nginx-ingress-controller Pods show RESTARTS The most common cause of this issue is the `canal` pods have failed to establish the overlay network. See [canal Pods show READY `2/3`](#canal-pods-show-ready-23) for troubleshooting. diff --git a/versioned_docs/version-2.12/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/troubleshooting.md b/versioned_docs/version-2.12/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/troubleshooting.md index b35276f8c5a..881a6d871a0 100644 --- a/versioned_docs/version-2.12/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/troubleshooting.md +++ b/versioned_docs/version-2.12/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/troubleshooting.md @@ -13,7 +13,7 @@ This section describes how to troubleshoot an installation of Rancher on a Kuber Most of the troubleshooting will be done on objects in these 3 namespaces. - `cattle-system` - `rancher` deployment and pods. -- `traefik` - Ingress controller pods and services. +- `ingress-nginx` - Ingress controller pods and services. - `cert-manager` - `cert-manager` pods. ### "default backend - 404" @@ -115,7 +115,7 @@ Events: Your certs get applied directly to the Ingress object in the `cattle-system` namespace. -Check the status of the Ingress object and see if it's ready. +Check the status of the Ingress object and see if its ready. ``` kubectl -n cattle-system describe ingress @@ -123,10 +123,12 @@ kubectl -n cattle-system describe ingress If its ready and the SSL is still not working you may have a malformed cert or secret. -Check the `traefik` logs. +Check the nginx-ingress-controller logs. Because the nginx-ingress-controller has multiple containers in its pod you will need to specify the name of the container. ``` -kubectl -n traefik logs +kubectl -n ingress-nginx logs -f nginx-ingress-controller-rfjrq nginx-ingress-controller +... +W0705 23:04:58.240571 7 backend_ssl.go:49] error obtaining PEM from secret cattle-system/tls-rancher-ingress: error retrieving secret cattle-system/tls-rancher-ingress: secret cattle-system/tls-rancher-ingress was not found ``` ### No matches for kind "Issuer" @@ -146,7 +148,7 @@ The most common cause of this issue is port 8472/UDP is not open between the nod Once the network issue is resolved, the `canal` pods should timeout and restart to establish their connections. -### Traefik Pods show RESTARTS +### nginx-ingress-controller Pods show RESTARTS The most common cause of this issue is the `canal` pods have failed to establish the overlay network. See [canal Pods show READY `2/3`](#canal-pods-show-ready-23) for troubleshooting. diff --git a/versioned_docs/version-2.13/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/troubleshooting.md b/versioned_docs/version-2.13/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/troubleshooting.md index b35276f8c5a..881a6d871a0 100644 --- a/versioned_docs/version-2.13/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/troubleshooting.md +++ b/versioned_docs/version-2.13/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/troubleshooting.md @@ -13,7 +13,7 @@ This section describes how to troubleshoot an installation of Rancher on a Kuber Most of the troubleshooting will be done on objects in these 3 namespaces. - `cattle-system` - `rancher` deployment and pods. -- `traefik` - Ingress controller pods and services. +- `ingress-nginx` - Ingress controller pods and services. - `cert-manager` - `cert-manager` pods. ### "default backend - 404" @@ -115,7 +115,7 @@ Events: Your certs get applied directly to the Ingress object in the `cattle-system` namespace. -Check the status of the Ingress object and see if it's ready. +Check the status of the Ingress object and see if its ready. ``` kubectl -n cattle-system describe ingress @@ -123,10 +123,12 @@ kubectl -n cattle-system describe ingress If its ready and the SSL is still not working you may have a malformed cert or secret. -Check the `traefik` logs. +Check the nginx-ingress-controller logs. Because the nginx-ingress-controller has multiple containers in its pod you will need to specify the name of the container. ``` -kubectl -n traefik logs +kubectl -n ingress-nginx logs -f nginx-ingress-controller-rfjrq nginx-ingress-controller +... +W0705 23:04:58.240571 7 backend_ssl.go:49] error obtaining PEM from secret cattle-system/tls-rancher-ingress: error retrieving secret cattle-system/tls-rancher-ingress: secret cattle-system/tls-rancher-ingress was not found ``` ### No matches for kind "Issuer" @@ -146,7 +148,7 @@ The most common cause of this issue is port 8472/UDP is not open between the nod Once the network issue is resolved, the `canal` pods should timeout and restart to establish their connections. -### Traefik Pods show RESTARTS +### nginx-ingress-controller Pods show RESTARTS The most common cause of this issue is the `canal` pods have failed to establish the overlay network. See [canal Pods show READY `2/3`](#canal-pods-show-ready-23) for troubleshooting. diff --git a/versioned_docs/version-2.14/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/troubleshooting.md b/versioned_docs/version-2.14/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/troubleshooting.md index b35276f8c5a..881a6d871a0 100644 --- a/versioned_docs/version-2.14/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/troubleshooting.md +++ b/versioned_docs/version-2.14/getting-started/installation-and-upgrade/install-upgrade-on-a-kubernetes-cluster/troubleshooting.md @@ -13,7 +13,7 @@ This section describes how to troubleshoot an installation of Rancher on a Kuber Most of the troubleshooting will be done on objects in these 3 namespaces. - `cattle-system` - `rancher` deployment and pods. -- `traefik` - Ingress controller pods and services. +- `ingress-nginx` - Ingress controller pods and services. - `cert-manager` - `cert-manager` pods. ### "default backend - 404" @@ -115,7 +115,7 @@ Events: Your certs get applied directly to the Ingress object in the `cattle-system` namespace. -Check the status of the Ingress object and see if it's ready. +Check the status of the Ingress object and see if its ready. ``` kubectl -n cattle-system describe ingress @@ -123,10 +123,12 @@ kubectl -n cattle-system describe ingress If its ready and the SSL is still not working you may have a malformed cert or secret. -Check the `traefik` logs. +Check the nginx-ingress-controller logs. Because the nginx-ingress-controller has multiple containers in its pod you will need to specify the name of the container. ``` -kubectl -n traefik logs +kubectl -n ingress-nginx logs -f nginx-ingress-controller-rfjrq nginx-ingress-controller +... +W0705 23:04:58.240571 7 backend_ssl.go:49] error obtaining PEM from secret cattle-system/tls-rancher-ingress: error retrieving secret cattle-system/tls-rancher-ingress: secret cattle-system/tls-rancher-ingress was not found ``` ### No matches for kind "Issuer" @@ -146,7 +148,7 @@ The most common cause of this issue is port 8472/UDP is not open between the nod Once the network issue is resolved, the `canal` pods should timeout and restart to establish their connections. -### Traefik Pods show RESTARTS +### nginx-ingress-controller Pods show RESTARTS The most common cause of this issue is the `canal` pods have failed to establish the overlay network. See [canal Pods show READY `2/3`](#canal-pods-show-ready-23) for troubleshooting.