From f25f4a404045a1a9c41eebabfdbd9580bf9f5a5a Mon Sep 17 00:00:00 2001 From: Sunil Singh Date: Wed, 20 May 2026 15:58:55 -0700 Subject: [PATCH 1/9] Update versions table Signed-off-by: Sunil Singh --- src/pages/versions.md | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/src/pages/versions.md b/src/pages/versions.md index 3bd55f669c2..63579ec4086 100644 --- a/src/pages/versions.md +++ b/src/pages/versions.md @@ -17,9 +17,9 @@ Here you can find links to supporting documentation for the current released ver Community - v2.14.1 + v2.14.2 Documentation - Release Notes + Release Notes
N/A
✓
✓
@@ -123,6 +123,14 @@ Here you can find links to supporting documentation for previous versions of Ran Prime Community + + v2.14.1 + Documentation + Release Notes +
Support Matrix
+
✓
+
✓
+ v2.14.0 Documentation From 7cc72a01c8b9eb273951c5dcbefaed9518d317d9 Mon Sep 17 00:00:00 2001 From: Sunil Singh Date: Wed, 20 May 2026 16:15:26 -0700 Subject: [PATCH 2/9] Update webhook Signed-off-by: Sunil Singh --- docs/reference-guides/rancher-webhook.md | 1 + .../current/reference-guides/rancher-webhook.md | 1 + .../version-2.14/reference-guides/rancher-webhook.md | 1 + versioned_docs/version-2.14/reference-guides/rancher-webhook.md | 1 + 4 files changed, 4 insertions(+) diff --git a/docs/reference-guides/rancher-webhook.md b/docs/reference-guides/rancher-webhook.md index dfe2e690e88..37dd19a6a1d 100644 --- a/docs/reference-guides/rancher-webhook.md +++ b/docs/reference-guides/rancher-webhook.md @@ -20,6 +20,7 @@ Each Rancher version is designed to be compatible with a single version of the w | Rancher Version | Webhook Version | Availability in Prime | Availability in Community | |-----------------|-----------------|-----------------------|---------------------------| +| v2.14.2 | v0.10.5 | ✓ | ✓ | | v2.14.1 | v0.10.1 | ✓ | ✓ | | v2.14.0 | v0.10.0 | ✗ | ✓ | diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/reference-guides/rancher-webhook.md b/i18n/zh/docusaurus-plugin-content-docs/current/reference-guides/rancher-webhook.md index 04d33f11c12..2b1d10e1975 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/current/reference-guides/rancher-webhook.md +++ b/i18n/zh/docusaurus-plugin-content-docs/current/reference-guides/rancher-webhook.md @@ -20,6 +20,7 @@ Rancher 将 Rancher-Webhook 作为单独的 deployment 和服务部署在 local | Rancher Version | Webhook Version | Availability in Prime | Availability in Community | |-----------------|-----------------|-----------------------|---------------------------| +| v2.14.2 | v0.10.5 | ✓ | ✓ | | v2.14.1 | v0.10.1 | ✓ | ✓ | | v2.14.0 | v0.10.0 | ✗ | ✓ | diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.14/reference-guides/rancher-webhook.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.14/reference-guides/rancher-webhook.md index 04d33f11c12..2b1d10e1975 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/version-2.14/reference-guides/rancher-webhook.md +++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.14/reference-guides/rancher-webhook.md @@ -20,6 +20,7 @@ Rancher 将 Rancher-Webhook 作为单独的 deployment 和服务部署在 local | Rancher Version | Webhook Version | Availability in Prime | Availability in Community | |-----------------|-----------------|-----------------------|---------------------------| +| v2.14.2 | v0.10.5 | ✓ | ✓ | | v2.14.1 | v0.10.1 | ✓ | ✓ | | v2.14.0 | v0.10.0 | ✗ | ✓ | diff --git a/versioned_docs/version-2.14/reference-guides/rancher-webhook.md b/versioned_docs/version-2.14/reference-guides/rancher-webhook.md index dfe2e690e88..37dd19a6a1d 100644 --- a/versioned_docs/version-2.14/reference-guides/rancher-webhook.md +++ b/versioned_docs/version-2.14/reference-guides/rancher-webhook.md @@ -20,6 +20,7 @@ Each Rancher version is designed to be compatible with a single version of the w | Rancher Version | Webhook Version | Availability in Prime | Availability in Community | |-----------------|-----------------|-----------------------|---------------------------| +| v2.14.2 | v0.10.5 | ✓ | ✓ | | v2.14.1 | v0.10.1 | ✓ | ✓ | | v2.14.0 | v0.10.0 | ✗ | ✓ | From 8798ed201641361be24c59ef6680e43e396dd28e Mon Sep 17 00:00:00 2001 From: Sunil Singh Date: Wed, 20 May 2026 16:26:13 -0700 Subject: [PATCH 3/9] Update CSP adapter Signed-off-by: Sunil Singh --- .../cloud-marketplace/aws-cloud-marketplace/install-adapter.md | 1 + .../cloud-marketplace/aws-cloud-marketplace/install-adapter.md | 1 + .../cloud-marketplace/aws-cloud-marketplace/install-adapter.md | 1 + .../cloud-marketplace/aws-cloud-marketplace/install-adapter.md | 1 + 4 files changed, 4 insertions(+) diff --git a/docs/integrations-in-rancher/cloud-marketplace/aws-cloud-marketplace/install-adapter.md b/docs/integrations-in-rancher/cloud-marketplace/aws-cloud-marketplace/install-adapter.md index 44705b904b8..91360501455 100644 --- a/docs/integrations-in-rancher/cloud-marketplace/aws-cloud-marketplace/install-adapter.md +++ b/docs/integrations-in-rancher/cloud-marketplace/aws-cloud-marketplace/install-adapter.md @@ -19,6 +19,7 @@ In order to deploy and run the adapter successfully, you need to ensure its vers | Rancher Version | Adapter Version | |-----------------|------------------| +| v2.14.2 | 109.0.0+up9.0.0 | | v2.14.1 | 109.0.0+up9.0.0 | | v2.14.0 | 109.0.0+up9.0.0 | diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/integrations-in-rancher/cloud-marketplace/aws-cloud-marketplace/install-adapter.md b/i18n/zh/docusaurus-plugin-content-docs/current/integrations-in-rancher/cloud-marketplace/aws-cloud-marketplace/install-adapter.md index 0ba877aac78..ea3a23df552 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/current/integrations-in-rancher/cloud-marketplace/aws-cloud-marketplace/install-adapter.md +++ b/i18n/zh/docusaurus-plugin-content-docs/current/integrations-in-rancher/cloud-marketplace/aws-cloud-marketplace/install-adapter.md @@ -15,6 +15,7 @@ title: 安装 Adapter | Rancher 版本 | Adapter 版本 | |-----------------|------------------| +| v2.14.2 | 109.0.0+up9.0.0 | | v2.14.1 | 109.0.0+up9.0.0 | | v2.14.0 | 109.0.0+up9.0.0 | diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.14/integrations-in-rancher/cloud-marketplace/aws-cloud-marketplace/install-adapter.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.14/integrations-in-rancher/cloud-marketplace/aws-cloud-marketplace/install-adapter.md index 0ba877aac78..ea3a23df552 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/version-2.14/integrations-in-rancher/cloud-marketplace/aws-cloud-marketplace/install-adapter.md +++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.14/integrations-in-rancher/cloud-marketplace/aws-cloud-marketplace/install-adapter.md @@ -15,6 +15,7 @@ title: 安装 Adapter | Rancher 版本 | Adapter 版本 | |-----------------|------------------| +| v2.14.2 | 109.0.0+up9.0.0 | | v2.14.1 | 109.0.0+up9.0.0 | | v2.14.0 | 109.0.0+up9.0.0 | diff --git a/versioned_docs/version-2.14/integrations-in-rancher/cloud-marketplace/aws-cloud-marketplace/install-adapter.md b/versioned_docs/version-2.14/integrations-in-rancher/cloud-marketplace/aws-cloud-marketplace/install-adapter.md index 44705b904b8..91360501455 100644 --- a/versioned_docs/version-2.14/integrations-in-rancher/cloud-marketplace/aws-cloud-marketplace/install-adapter.md +++ b/versioned_docs/version-2.14/integrations-in-rancher/cloud-marketplace/aws-cloud-marketplace/install-adapter.md @@ -19,6 +19,7 @@ In order to deploy and run the adapter successfully, you need to ensure its vers | Rancher Version | Adapter Version | |-----------------|------------------| +| v2.14.2 | 109.0.0+up9.0.0 | | v2.14.1 | 109.0.0+up9.0.0 | | v2.14.0 | 109.0.0+up9.0.0 | From 2360f9a7b99683e9ee028486f4f74516c7aaa80d Mon Sep 17 00:00:00 2001 From: Sunil Singh Date: Wed, 20 May 2026 16:30:52 -0700 Subject: [PATCH 4/9] Update CNI popularity table Signed-off-by: Sunil Singh --- shared-files/_cni-popularity.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/shared-files/_cni-popularity.md b/shared-files/_cni-popularity.md index f02f5b68f33..e1f55fa96e1 100644 --- a/shared-files/_cni-popularity.md +++ b/shared-files/_cni-popularity.md @@ -1,10 +1,10 @@ -The following table summarizes different GitHub metrics to give you an idea of each project's popularity and activity levels. This data was collected in December 2025. +The following table summarizes different GitHub metrics to give you an idea of each project's popularity and activity levels. This data was collected in May 2026. | Provider | Project | Stars | Forks | Contributors | | ---- | ---- | ---- | ---- | ---- | -| Canal | https://github.com/projectcalico/canal | 722 | 97 | 20 | -| Flannel | https://github.com/flannel-io/flannel | 9.4k | 2.9k | 248 | +| Canal | https://github.com/projectcalico/canal | 723 | 97 | 20 | +| Flannel | https://github.com/flannel-io/flannel | 9.5k | 2.9k | 249 | | Calico | https://github.com/projectcalico/calico | 7.2k | 1.6k | 412 | | Weave | https://github.com/weaveworks/weave | 6.6k | 675 | 82 | -| Cilium | https://github.com/cilium/cilium | 24.2k | 3.7k | 1067 | +| Cilium | https://github.com/cilium/cilium | 24.4k | 3.8k | 1085 | From 5493a494d87d34842bd66a6d800b72e41828bb44 Mon Sep 17 00:00:00 2001 From: Sunil Singh Date: Wed, 20 May 2026 16:34:25 -0700 Subject: [PATCH 5/9] Update deprecated features table Signed-off-by: Sunil Singh --- docs/faq/deprecated-features.md | 1 + .../current/faq/deprecated-features.md | 1 + .../version-2.14/faq/deprecated-features.md | 1 + versioned_docs/version-2.14/faq/deprecated-features.md | 1 + 4 files changed, 4 insertions(+) diff --git a/docs/faq/deprecated-features.md b/docs/faq/deprecated-features.md index 2ce43ccc28b..0397e3cf8f2 100644 --- a/docs/faq/deprecated-features.md +++ b/docs/faq/deprecated-features.md @@ -12,6 +12,7 @@ Rancher will publish deprecated features as part of the [release notes](https:// | Patch Version | Release Date | |---------------|---------------| +| [2.14.2](https://github.com/rancher/rancher/releases/tag/v2.14.2) | May 27, 2026 | | [2.14.1](https://github.com/rancher/rancher/releases/tag/v2.14.1) | April 30, 2026 | | [2.14.0](https://github.com/rancher/rancher/releases/tag/v2.14.0) | March 25, 2026 | diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/faq/deprecated-features.md b/i18n/zh/docusaurus-plugin-content-docs/current/faq/deprecated-features.md index 7ef39399ce3..d55b2fa523c 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/current/faq/deprecated-features.md +++ b/i18n/zh/docusaurus-plugin-content-docs/current/faq/deprecated-features.md @@ -12,6 +12,7 @@ Rancher 将在 GitHub 上发布的 Rancher 的[发版说明](https://github.com/ | Patch 版本 | 发布时间 | | ----------------------------------------------------------------- | ------------------ | +| [2.14.2](https://github.com/rancher/rancher/releases/tag/v2.14.2) | 2026 年 05 月 27 日 | | [2.14.1](https://github.com/rancher/rancher/releases/tag/v2.14.1) | 2026 年 04 月 30 日 | | [2.14.0](https://github.com/rancher/rancher/releases/tag/v2.14.0) | 2026 年 03 月 25 日 | diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.14/faq/deprecated-features.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.14/faq/deprecated-features.md index 7ef39399ce3..d55b2fa523c 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/version-2.14/faq/deprecated-features.md +++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.14/faq/deprecated-features.md @@ -12,6 +12,7 @@ Rancher 将在 GitHub 上发布的 Rancher 的[发版说明](https://github.com/ | Patch 版本 | 发布时间 | | ----------------------------------------------------------------- | ------------------ | +| [2.14.2](https://github.com/rancher/rancher/releases/tag/v2.14.2) | 2026 年 05 月 27 日 | | [2.14.1](https://github.com/rancher/rancher/releases/tag/v2.14.1) | 2026 年 04 月 30 日 | | [2.14.0](https://github.com/rancher/rancher/releases/tag/v2.14.0) | 2026 年 03 月 25 日 | diff --git a/versioned_docs/version-2.14/faq/deprecated-features.md b/versioned_docs/version-2.14/faq/deprecated-features.md index 6e92f5732d4..77b9f22fc23 100644 --- a/versioned_docs/version-2.14/faq/deprecated-features.md +++ b/versioned_docs/version-2.14/faq/deprecated-features.md @@ -12,6 +12,7 @@ Rancher will publish deprecated features as part of the [release notes](https:// | Patch Version | Release Date | |---------------|---------------| +| [2.14.2](https://github.com/rancher/rancher/releases/tag/v2.14.2) | May 27, 2026 | | [2.14.1](https://github.com/rancher/rancher/releases/tag/v2.14.1) | April 30, 2026 | | [2.14.0](https://github.com/rancher/rancher/releases/tag/v2.14.0) | March 25, 2026 | From 97c7ee878ed6d258b87da8ac263fd1fe95533c2f Mon Sep 17 00:00:00 2001 From: Sunil Singh Date: Fri, 22 May 2026 09:40:46 -0700 Subject: [PATCH 6/9] Adding troubleshooting info to logging page - inotify system update Signed-off-by: Sunil Singh --- docs/integrations-in-rancher/logging/logging.md | 13 +++++++++++++ .../integrations-in-rancher/logging/logging.md | 13 +++++++++++++ .../integrations-in-rancher/logging/logging.md | 13 +++++++++++++ .../integrations-in-rancher/logging/logging.md | 13 +++++++++++++ .../integrations-in-rancher/logging/logging.md | 13 +++++++++++++ .../integrations-in-rancher/logging/logging.md | 13 +++++++++++++ .../integrations-in-rancher/logging/logging.md | 13 +++++++++++++ .../integrations-in-rancher/logging/logging.md | 13 +++++++++++++ .../integrations-in-rancher/logging/logging.md | 13 +++++++++++++ .../integrations-in-rancher/logging/logging.md | 13 +++++++++++++ .../integrations-in-rancher/logging/logging.md | 13 +++++++++++++ .../integrations-in-rancher/logging/logging.md | 13 +++++++++++++ 12 files changed, 156 insertions(+) diff --git a/docs/integrations-in-rancher/logging/logging.md b/docs/integrations-in-rancher/logging/logging.md index 217f64f9019..bc6bd4470b2 100644 --- a/docs/integrations-in-rancher/logging/logging.md +++ b/docs/integrations-in-rancher/logging/logging.md @@ -116,6 +116,19 @@ By default, Rancher collects logs for control plane components and node componen ## Troubleshooting +### Resource Exhaustion of `inotify` Watchers and File Descriptors + +When enabling the **Logging** app on Linux systems that heavily monitor the filesystem, you may encounter `Too many open files` or `CrashLoopBackOff` failures related to applications that leverage `inotify` to watch for file changes. + +This happens because the Linux kernel caps the number of files a user can open and the number of directory paths a subsystem can watch simultaneously. To resolve this, you must explicitly increase your `inotify` system limits. + +Below are example commands an admin user can run to increase system limits for `inotify` user instances and watches: + +```shell +sysctl -w fs.inotify.max_user_instances=8192 +sysctl -w fs.inotify.max_user_watches=524288 +``` + ### The Logging Buffer Overloads Pods Depending on your configuration, the default buffer size may be too large and cause pod failures. One way to reduce the load is to lower the logger's flush interval. This prevents logs from overfilling the buffer. You can also add more flush threads to handle moments when many logs are attempting to fill the buffer at once. diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/integrations-in-rancher/logging/logging.md b/i18n/zh/docusaurus-plugin-content-docs/current/integrations-in-rancher/logging/logging.md index dcc65014fbd..63c0caf8d1a 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/current/integrations-in-rancher/logging/logging.md +++ b/i18n/zh/docusaurus-plugin-content-docs/current/integrations-in-rancher/logging/logging.md @@ -79,6 +79,19 @@ Rancher Logging 有两个角色，分别是 `logging-admin` 和 `logging-view` ## 故障排除 +### Resource Exhaustion of `inotify` Watchers and File Descriptors + +When enabling the **Logging** app on Linux systems that heavily monitor the filesystem, you may encounter `Too many open files` or `CrashLoopBackOff` failures related to applications that leverage `inotify` to watch for file changes. + +This happens because the Linux kernel caps the number of files a user can open and the number of directory paths a subsystem can watch simultaneously. To resolve this, you must explicitly increase your `inotify` system limits. + +Below are example commands an admin user can run to increase system limits for `inotify` user instances and watches: + +```shell +sysctl -w fs.inotify.max_user_instances=8192 +sysctl -w fs.inotify.max_user_watches=524288 +``` + ### 日志缓冲区导致 Pod 过载 根据你的配置，默认缓冲区大小可能太大并导致 Pod 故障。减少负载的一种方法是降低记录器的刷新间隔。这可以防止日志溢出缓冲区。你还可以添加更多刷新线程来处理大量日志试图同时填充缓冲区的情况。 diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.10/integrations-in-rancher/logging/logging.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.10/integrations-in-rancher/logging/logging.md index dcc65014fbd..63c0caf8d1a 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/version-2.10/integrations-in-rancher/logging/logging.md +++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.10/integrations-in-rancher/logging/logging.md @@ -79,6 +79,19 @@ Rancher Logging 有两个角色，分别是 `logging-admin` 和 `logging-view` ## 故障排除 +### Resource Exhaustion of `inotify` Watchers and File Descriptors + +When enabling the **Logging** app on Linux systems that heavily monitor the filesystem, you may encounter `Too many open files` or `CrashLoopBackOff` failures related to applications that leverage `inotify` to watch for file changes. + +This happens because the Linux kernel caps the number of files a user can open and the number of directory paths a subsystem can watch simultaneously. To resolve this, you must explicitly increase your `inotify` system limits. + +Below are example commands an admin user can run to increase system limits for `inotify` user instances and watches: + +```shell +sysctl -w fs.inotify.max_user_instances=8192 +sysctl -w fs.inotify.max_user_watches=524288 +``` + ### 日志缓冲区导致 Pod 过载 根据你的配置，默认缓冲区大小可能太大并导致 Pod 故障。减少负载的一种方法是降低记录器的刷新间隔。这可以防止日志溢出缓冲区。你还可以添加更多刷新线程来处理大量日志试图同时填充缓冲区的情况。 diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.11/integrations-in-rancher/logging/logging.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.11/integrations-in-rancher/logging/logging.md index dcc65014fbd..63c0caf8d1a 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/version-2.11/integrations-in-rancher/logging/logging.md +++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.11/integrations-in-rancher/logging/logging.md @@ -79,6 +79,19 @@ Rancher Logging 有两个角色，分别是 `logging-admin` 和 `logging-view` ## 故障排除 +### Resource Exhaustion of `inotify` Watchers and File Descriptors + +When enabling the **Logging** app on Linux systems that heavily monitor the filesystem, you may encounter `Too many open files` or `CrashLoopBackOff` failures related to applications that leverage `inotify` to watch for file changes. + +This happens because the Linux kernel caps the number of files a user can open and the number of directory paths a subsystem can watch simultaneously. To resolve this, you must explicitly increase your `inotify` system limits. + +Below are example commands an admin user can run to increase system limits for `inotify` user instances and watches: + +```shell +sysctl -w fs.inotify.max_user_instances=8192 +sysctl -w fs.inotify.max_user_watches=524288 +``` + ### 日志缓冲区导致 Pod 过载 根据你的配置，默认缓冲区大小可能太大并导致 Pod 故障。减少负载的一种方法是降低记录器的刷新间隔。这可以防止日志溢出缓冲区。你还可以添加更多刷新线程来处理大量日志试图同时填充缓冲区的情况。 diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.12/integrations-in-rancher/logging/logging.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.12/integrations-in-rancher/logging/logging.md index dcc65014fbd..63c0caf8d1a 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/version-2.12/integrations-in-rancher/logging/logging.md +++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.12/integrations-in-rancher/logging/logging.md @@ -79,6 +79,19 @@ Rancher Logging 有两个角色，分别是 `logging-admin` 和 `logging-view` ## 故障排除 +### Resource Exhaustion of `inotify` Watchers and File Descriptors + +When enabling the **Logging** app on Linux systems that heavily monitor the filesystem, you may encounter `Too many open files` or `CrashLoopBackOff` failures related to applications that leverage `inotify` to watch for file changes. + +This happens because the Linux kernel caps the number of files a user can open and the number of directory paths a subsystem can watch simultaneously. To resolve this, you must explicitly increase your `inotify` system limits. + +Below are example commands an admin user can run to increase system limits for `inotify` user instances and watches: + +```shell +sysctl -w fs.inotify.max_user_instances=8192 +sysctl -w fs.inotify.max_user_watches=524288 +``` + ### 日志缓冲区导致 Pod 过载 根据你的配置，默认缓冲区大小可能太大并导致 Pod 故障。减少负载的一种方法是降低记录器的刷新间隔。这可以防止日志溢出缓冲区。你还可以添加更多刷新线程来处理大量日志试图同时填充缓冲区的情况。 diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.13/integrations-in-rancher/logging/logging.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.13/integrations-in-rancher/logging/logging.md index dcc65014fbd..63c0caf8d1a 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/version-2.13/integrations-in-rancher/logging/logging.md +++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.13/integrations-in-rancher/logging/logging.md @@ -79,6 +79,19 @@ Rancher Logging 有两个角色，分别是 `logging-admin` 和 `logging-view` ## 故障排除 +### Resource Exhaustion of `inotify` Watchers and File Descriptors + +When enabling the **Logging** app on Linux systems that heavily monitor the filesystem, you may encounter `Too many open files` or `CrashLoopBackOff` failures related to applications that leverage `inotify` to watch for file changes. + +This happens because the Linux kernel caps the number of files a user can open and the number of directory paths a subsystem can watch simultaneously. To resolve this, you must explicitly increase your `inotify` system limits. + +Below are example commands an admin user can run to increase system limits for `inotify` user instances and watches: + +```shell +sysctl -w fs.inotify.max_user_instances=8192 +sysctl -w fs.inotify.max_user_watches=524288 +``` + ### 日志缓冲区导致 Pod 过载 根据你的配置，默认缓冲区大小可能太大并导致 Pod 故障。减少负载的一种方法是降低记录器的刷新间隔。这可以防止日志溢出缓冲区。你还可以添加更多刷新线程来处理大量日志试图同时填充缓冲区的情况。 diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.14/integrations-in-rancher/logging/logging.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.14/integrations-in-rancher/logging/logging.md index dcc65014fbd..63c0caf8d1a 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/version-2.14/integrations-in-rancher/logging/logging.md +++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.14/integrations-in-rancher/logging/logging.md @@ -79,6 +79,19 @@ Rancher Logging 有两个角色，分别是 `logging-admin` 和 `logging-view` ## 故障排除 +### Resource Exhaustion of `inotify` Watchers and File Descriptors + +When enabling the **Logging** app on Linux systems that heavily monitor the filesystem, you may encounter `Too many open files` or `CrashLoopBackOff` failures related to applications that leverage `inotify` to watch for file changes. + +This happens because the Linux kernel caps the number of files a user can open and the number of directory paths a subsystem can watch simultaneously. To resolve this, you must explicitly increase your `inotify` system limits. + +Below are example commands an admin user can run to increase system limits for `inotify` user instances and watches: + +```shell +sysctl -w fs.inotify.max_user_instances=8192 +sysctl -w fs.inotify.max_user_watches=524288 +``` + ### 日志缓冲区导致 Pod 过载 根据你的配置，默认缓冲区大小可能太大并导致 Pod 故障。减少负载的一种方法是降低记录器的刷新间隔。这可以防止日志溢出缓冲区。你还可以添加更多刷新线程来处理大量日志试图同时填充缓冲区的情况。 diff --git a/versioned_docs/version-2.10/integrations-in-rancher/logging/logging.md b/versioned_docs/version-2.10/integrations-in-rancher/logging/logging.md index 217f64f9019..bc6bd4470b2 100644 --- a/versioned_docs/version-2.10/integrations-in-rancher/logging/logging.md +++ b/versioned_docs/version-2.10/integrations-in-rancher/logging/logging.md @@ -116,6 +116,19 @@ By default, Rancher collects logs for control plane components and node componen ## Troubleshooting +### Resource Exhaustion of `inotify` Watchers and File Descriptors + +When enabling the **Logging** app on Linux systems that heavily monitor the filesystem, you may encounter `Too many open files` or `CrashLoopBackOff` failures related to applications that leverage `inotify` to watch for file changes. + +This happens because the Linux kernel caps the number of files a user can open and the number of directory paths a subsystem can watch simultaneously. To resolve this, you must explicitly increase your `inotify` system limits. + +Below are example commands an admin user can run to increase system limits for `inotify` user instances and watches: + +```shell +sysctl -w fs.inotify.max_user_instances=8192 +sysctl -w fs.inotify.max_user_watches=524288 +``` + ### The Logging Buffer Overloads Pods Depending on your configuration, the default buffer size may be too large and cause pod failures. One way to reduce the load is to lower the logger's flush interval. This prevents logs from overfilling the buffer. You can also add more flush threads to handle moments when many logs are attempting to fill the buffer at once. diff --git a/versioned_docs/version-2.11/integrations-in-rancher/logging/logging.md b/versioned_docs/version-2.11/integrations-in-rancher/logging/logging.md index 217f64f9019..bc6bd4470b2 100644 --- a/versioned_docs/version-2.11/integrations-in-rancher/logging/logging.md +++ b/versioned_docs/version-2.11/integrations-in-rancher/logging/logging.md @@ -116,6 +116,19 @@ By default, Rancher collects logs for control plane components and node componen ## Troubleshooting +### Resource Exhaustion of `inotify` Watchers and File Descriptors + +When enabling the **Logging** app on Linux systems that heavily monitor the filesystem, you may encounter `Too many open files` or `CrashLoopBackOff` failures related to applications that leverage `inotify` to watch for file changes. + +This happens because the Linux kernel caps the number of files a user can open and the number of directory paths a subsystem can watch simultaneously. To resolve this, you must explicitly increase your `inotify` system limits. + +Below are example commands an admin user can run to increase system limits for `inotify` user instances and watches: + +```shell +sysctl -w fs.inotify.max_user_instances=8192 +sysctl -w fs.inotify.max_user_watches=524288 +``` + ### The Logging Buffer Overloads Pods Depending on your configuration, the default buffer size may be too large and cause pod failures. One way to reduce the load is to lower the logger's flush interval. This prevents logs from overfilling the buffer. You can also add more flush threads to handle moments when many logs are attempting to fill the buffer at once. diff --git a/versioned_docs/version-2.12/integrations-in-rancher/logging/logging.md b/versioned_docs/version-2.12/integrations-in-rancher/logging/logging.md index 217f64f9019..bc6bd4470b2 100644 --- a/versioned_docs/version-2.12/integrations-in-rancher/logging/logging.md +++ b/versioned_docs/version-2.12/integrations-in-rancher/logging/logging.md @@ -116,6 +116,19 @@ By default, Rancher collects logs for control plane components and node componen ## Troubleshooting +### Resource Exhaustion of `inotify` Watchers and File Descriptors + +When enabling the **Logging** app on Linux systems that heavily monitor the filesystem, you may encounter `Too many open files` or `CrashLoopBackOff` failures related to applications that leverage `inotify` to watch for file changes. + +This happens because the Linux kernel caps the number of files a user can open and the number of directory paths a subsystem can watch simultaneously. To resolve this, you must explicitly increase your `inotify` system limits. + +Below are example commands an admin user can run to increase system limits for `inotify` user instances and watches: + +```shell +sysctl -w fs.inotify.max_user_instances=8192 +sysctl -w fs.inotify.max_user_watches=524288 +``` + ### The Logging Buffer Overloads Pods Depending on your configuration, the default buffer size may be too large and cause pod failures. One way to reduce the load is to lower the logger's flush interval. This prevents logs from overfilling the buffer. You can also add more flush threads to handle moments when many logs are attempting to fill the buffer at once. diff --git a/versioned_docs/version-2.13/integrations-in-rancher/logging/logging.md b/versioned_docs/version-2.13/integrations-in-rancher/logging/logging.md index 217f64f9019..bc6bd4470b2 100644 --- a/versioned_docs/version-2.13/integrations-in-rancher/logging/logging.md +++ b/versioned_docs/version-2.13/integrations-in-rancher/logging/logging.md @@ -116,6 +116,19 @@ By default, Rancher collects logs for control plane components and node componen ## Troubleshooting +### Resource Exhaustion of `inotify` Watchers and File Descriptors + +When enabling the **Logging** app on Linux systems that heavily monitor the filesystem, you may encounter `Too many open files` or `CrashLoopBackOff` failures related to applications that leverage `inotify` to watch for file changes. + +This happens because the Linux kernel caps the number of files a user can open and the number of directory paths a subsystem can watch simultaneously. To resolve this, you must explicitly increase your `inotify` system limits. + +Below are example commands an admin user can run to increase system limits for `inotify` user instances and watches: + +```shell +sysctl -w fs.inotify.max_user_instances=8192 +sysctl -w fs.inotify.max_user_watches=524288 +``` + ### The Logging Buffer Overloads Pods Depending on your configuration, the default buffer size may be too large and cause pod failures. One way to reduce the load is to lower the logger's flush interval. This prevents logs from overfilling the buffer. You can also add more flush threads to handle moments when many logs are attempting to fill the buffer at once. diff --git a/versioned_docs/version-2.14/integrations-in-rancher/logging/logging.md b/versioned_docs/version-2.14/integrations-in-rancher/logging/logging.md index 217f64f9019..bc6bd4470b2 100644 --- a/versioned_docs/version-2.14/integrations-in-rancher/logging/logging.md +++ b/versioned_docs/version-2.14/integrations-in-rancher/logging/logging.md @@ -116,6 +116,19 @@ By default, Rancher collects logs for control plane components and node componen ## Troubleshooting +### Resource Exhaustion of `inotify` Watchers and File Descriptors + +When enabling the **Logging** app on Linux systems that heavily monitor the filesystem, you may encounter `Too many open files` or `CrashLoopBackOff` failures related to applications that leverage `inotify` to watch for file changes. + +This happens because the Linux kernel caps the number of files a user can open and the number of directory paths a subsystem can watch simultaneously. To resolve this, you must explicitly increase your `inotify` system limits. + +Below are example commands an admin user can run to increase system limits for `inotify` user instances and watches: + +```shell +sysctl -w fs.inotify.max_user_instances=8192 +sysctl -w fs.inotify.max_user_watches=524288 +``` + ### The Logging Buffer Overloads Pods Depending on your configuration, the default buffer size may be too large and cause pod failures. One way to reduce the load is to lower the logger's flush interval. This prevents logs from overfilling the buffer. You can also add more flush threads to handle moments when many logs are attempting to fill the buffer at once. From b15636ea3b64dac29d574f727931fd97cd251c48 Mon Sep 17 00:00:00 2001 From: Sunil Singh Date: Tue, 26 May 2026 09:53:26 -0700 Subject: [PATCH 7/9] Update webhook v2.14.2 Signed-off-by: Sunil Singh --- docs/reference-guides/rancher-webhook.md | 2 +- versioned_docs/version-2.14/reference-guides/rancher-webhook.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/reference-guides/rancher-webhook.md b/docs/reference-guides/rancher-webhook.md index 37dd19a6a1d..23bc5cfd6e4 100644 --- a/docs/reference-guides/rancher-webhook.md +++ b/docs/reference-guides/rancher-webhook.md @@ -21,7 +21,7 @@ Each Rancher version is designed to be compatible with a single version of the w | Rancher Version | Webhook Version | Availability in Prime | Availability in Community | |-----------------|-----------------|-----------------------|---------------------------| | v2.14.2 | v0.10.5 | ✓ | ✓ | -| v2.14.1 | v0.10.1 | ✓ | ✓ | +| v2.14.1 | v0.10.4 | ✓ | ✓ | | v2.14.0 | v0.10.0 | ✗ | ✓ | ## Why Do We Need It? diff --git a/versioned_docs/version-2.14/reference-guides/rancher-webhook.md b/versioned_docs/version-2.14/reference-guides/rancher-webhook.md index 37dd19a6a1d..23bc5cfd6e4 100644 --- a/versioned_docs/version-2.14/reference-guides/rancher-webhook.md +++ b/versioned_docs/version-2.14/reference-guides/rancher-webhook.md @@ -21,7 +21,7 @@ Each Rancher version is designed to be compatible with a single version of the w | Rancher Version | Webhook Version | Availability in Prime | Availability in Community | |-----------------|-----------------|-----------------------|---------------------------| | v2.14.2 | v0.10.5 | ✓ | ✓ | -| v2.14.1 | v0.10.1 | ✓ | ✓ | +| v2.14.1 | v0.10.4 | ✓ | ✓ | | v2.14.0 | v0.10.0 | ✗ | ✓ | ## Why Do We Need It? From e348d8ae96d49fc6066838a63bfa37ac46db5db2 Mon Sep 17 00:00:00 2001 From: Sunil Singh Date: Tue, 26 May 2026 09:59:13 -0700 Subject: [PATCH 8/9] Update webhook Signed-off-by: Sunil Singh --- .../current/reference-guides/rancher-webhook.md | 2 +- .../version-2.14/reference-guides/rancher-webhook.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/reference-guides/rancher-webhook.md b/i18n/zh/docusaurus-plugin-content-docs/current/reference-guides/rancher-webhook.md index 2b1d10e1975..ab94fdc85e8 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/current/reference-guides/rancher-webhook.md +++ b/i18n/zh/docusaurus-plugin-content-docs/current/reference-guides/rancher-webhook.md @@ -21,7 +21,7 @@ Rancher 将 Rancher-Webhook 作为单独的 deployment 和服务部署在 local | Rancher Version | Webhook Version | Availability in Prime | Availability in Community | |-----------------|-----------------|-----------------------|---------------------------| | v2.14.2 | v0.10.5 | ✓ | ✓ | -| v2.14.1 | v0.10.1 | ✓ | ✓ | +| v2.14.1 | v0.10.4 | ✓ | ✓ | | v2.14.0 | v0.10.0 | ✗ | ✓ | ## 为什么我们需要它？ diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.14/reference-guides/rancher-webhook.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.14/reference-guides/rancher-webhook.md index 2b1d10e1975..ab94fdc85e8 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/version-2.14/reference-guides/rancher-webhook.md +++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.14/reference-guides/rancher-webhook.md @@ -21,7 +21,7 @@ Rancher 将 Rancher-Webhook 作为单独的 deployment 和服务部署在 local | Rancher Version | Webhook Version | Availability in Prime | Availability in Community | |-----------------|-----------------|-----------------------|---------------------------| | v2.14.2 | v0.10.5 | ✓ | ✓ | -| v2.14.1 | v0.10.1 | ✓ | ✓ | +| v2.14.1 | v0.10.4 | ✓ | ✓ | | v2.14.0 | v0.10.0 | ✗ | ✓ | ## 为什么我们需要它？ From c15221a43f5ac76b10fdf42355f8229769fc98f6 Mon Sep 17 00:00:00 2001 From: Sunil Singh Date: Thu, 28 May 2026 08:35:35 -0700 Subject: [PATCH 9/9] Updating community release date Signed-off-by: Sunil Singh --- docs/faq/deprecated-features.md | 2 +- .../current/faq/deprecated-features.md | 2 +- .../version-2.14/faq/deprecated-features.md | 2 +- versioned_docs/version-2.14/faq/deprecated-features.md | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/faq/deprecated-features.md b/docs/faq/deprecated-features.md index 0397e3cf8f2..34ed18f7fc2 100644 --- a/docs/faq/deprecated-features.md +++ b/docs/faq/deprecated-features.md @@ -12,7 +12,7 @@ Rancher will publish deprecated features as part of the [release notes](https:// | Patch Version | Release Date | |---------------|---------------| -| [2.14.2](https://github.com/rancher/rancher/releases/tag/v2.14.2) | May 27, 2026 | +| [2.14.2](https://github.com/rancher/rancher/releases/tag/v2.14.2) | May 28, 2026 | | [2.14.1](https://github.com/rancher/rancher/releases/tag/v2.14.1) | April 30, 2026 | | [2.14.0](https://github.com/rancher/rancher/releases/tag/v2.14.0) | March 25, 2026 | diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/faq/deprecated-features.md b/i18n/zh/docusaurus-plugin-content-docs/current/faq/deprecated-features.md index d55b2fa523c..b87b3441e1c 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/current/faq/deprecated-features.md +++ b/i18n/zh/docusaurus-plugin-content-docs/current/faq/deprecated-features.md @@ -12,7 +12,7 @@ Rancher 将在 GitHub 上发布的 Rancher 的[发版说明](https://github.com/ | Patch 版本 | 发布时间 | | ----------------------------------------------------------------- | ------------------ | -| [2.14.2](https://github.com/rancher/rancher/releases/tag/v2.14.2) | 2026 年 05 月 27 日 | +| [2.14.2](https://github.com/rancher/rancher/releases/tag/v2.14.2) | 2026 年 05 月 28 日 | | [2.14.1](https://github.com/rancher/rancher/releases/tag/v2.14.1) | 2026 年 04 月 30 日 | | [2.14.0](https://github.com/rancher/rancher/releases/tag/v2.14.0) | 2026 年 03 月 25 日 | diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.14/faq/deprecated-features.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.14/faq/deprecated-features.md index d55b2fa523c..b87b3441e1c 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/version-2.14/faq/deprecated-features.md +++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.14/faq/deprecated-features.md @@ -12,7 +12,7 @@ Rancher 将在 GitHub 上发布的 Rancher 的[发版说明](https://github.com/ | Patch 版本 | 发布时间 | | ----------------------------------------------------------------- | ------------------ | -| [2.14.2](https://github.com/rancher/rancher/releases/tag/v2.14.2) | 2026 年 05 月 27 日 | +| [2.14.2](https://github.com/rancher/rancher/releases/tag/v2.14.2) | 2026 年 05 月 28 日 | | [2.14.1](https://github.com/rancher/rancher/releases/tag/v2.14.1) | 2026 年 04 月 30 日 | | [2.14.0](https://github.com/rancher/rancher/releases/tag/v2.14.0) | 2026 年 03 月 25 日 | diff --git a/versioned_docs/version-2.14/faq/deprecated-features.md b/versioned_docs/version-2.14/faq/deprecated-features.md index 77b9f22fc23..f6fa35f45e5 100644 --- a/versioned_docs/version-2.14/faq/deprecated-features.md +++ b/versioned_docs/version-2.14/faq/deprecated-features.md @@ -12,7 +12,7 @@ Rancher will publish deprecated features as part of the [release notes](https:// | Patch Version | Release Date | |---------------|---------------| -| [2.14.2](https://github.com/rancher/rancher/releases/tag/v2.14.2) | May 27, 2026 | +| [2.14.2](https://github.com/rancher/rancher/releases/tag/v2.14.2) | May 28, 2026 | | [2.14.1](https://github.com/rancher/rancher/releases/tag/v2.14.1) | April 30, 2026 | | [2.14.0](https://github.com/rancher/rancher/releases/tag/v2.14.0) | March 25, 2026 |