diff --git a/docs/integrations-in-rancher/monitoring-and-alerting/windows-support.md b/docs/integrations-in-rancher/monitoring-and-alerting/windows-support.md index 7f93c644ab2..db1dfb8bfa3 100644 --- a/docs/integrations-in-rancher/monitoring-and-alerting/windows-support.md +++ b/docs/integrations-in-rancher/monitoring-and-alerting/windows-support.md @@ -12,8 +12,6 @@ Monitoring V2 can be deployed on a Windows cluster to scrape metrics from Window Monitoring V2 for Windows can only scrape metrics from Windows hosts that have a minimum `wins` version of v0.1.0. To be able to fully deploy Monitoring V2 for Windows, all of your hosts must meet this requirement. -If you provision a fresh RKE1 cluster in Rancher 2.5.8, your cluster should already meet this requirement. - ### Upgrading Existing Clusters to wins v0.1.0 If the cluster was provisioned before Rancher 2.5.8 (even if the current Rancher version is 2.5.8), you will not be able to successfully deploy Monitoring V2 for Windows until you upgrade the wins version on each host to at least v0.1.0. @@ -21,6 +19,7 @@ If the cluster was provisioned before Rancher 2.5.8 (even if the current Rancher To facilitate this upgrade, Rancher 2.5.8 has released a brand new Helm chart called `rancher-wins-upgrader`. 1. Deploy `rancher-wins-upgrader` with the following override: + ```yaml # Masquerading bootstraps the wins-upgrader installation via # a previously whitelisted process path since the normal install path, @@ -31,15 +30,9 @@ To facilitate this upgrade, Rancher 2.5.8 has released a brand new Helm chart ca enabled: true as: c:\\etc\wmi-exporter\wmi-exporter.exe ``` - :::note Note for Non-Default Windows Prefix Path: - - - If you set up the RKE cluster with a `cluster.yml` that has a non-default `win_prefix_path`, you will need to update the `masquerade.as` field with your prefix path in place of `c:\\`. - - - For example, if you have `win_prefix_path: 'c:\host\opt\'`, then you will need to set `as: c:\host\opt\etc\wmi-exporter\wmi-exporter.exe`. - - ::: 2. Once all your hosts have been successfully upgraded, please ensure that you deploy the Helm chart once again with default values to avoid conflicts with the following settings: + ```yaml masquerade: enabled: false diff --git a/i18n/zh/docusaurus-plugin-content-docs/current/integrations-in-rancher/monitoring-and-alerting/windows-support.md b/i18n/zh/docusaurus-plugin-content-docs/current/integrations-in-rancher/monitoring-and-alerting/windows-support.md index c8de9476221..c46c0cc8f76 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/current/integrations-in-rancher/monitoring-and-alerting/windows-support.md +++ b/i18n/zh/docusaurus-plugin-content-docs/current/integrations-in-rancher/monitoring-and-alerting/windows-support.md @@ -10,8 +10,6 @@ _从 v2.5.8 起可用_ Monitoring V2 for Windows 只能从最低是 `wins` v0.1.0 的 Windows 主机中抓取指标。要完全部署 Monitoring V2 for Windows，你的所有主机都必须满足此要求。 -如果你在 Rancher 2.5.8 中配置新的 RKE1 集群，你的集群应该已经满足此要求。 - ### 将现有集群升级到 wins v0.1.0 如果集群是在 Rancher 2.5.8 之前配置的（即使当前 Rancher 版本是 2.5.8），你将无法成功部署 Monitoring V2 for Windows，除非你将每台主机的 wins 版本升级到 v0.1.0 或以上版本。 @@ -19,6 +17,7 @@ Monitoring V2 for Windows 只能从最低是 `wins` v0.1.0 的 Windows 主机中 为了方便此次升级，Rancher 2.5.8 发布了一个全新的 Helm Chart，名为 `rancher-wins-upgrader`。 1. 使用以下覆盖部署 `rancher-wins-upgrader`： + ```yaml # 通过先前已列入白名单的进程路径 # 来引导 win-upgrader 安装，这是因为正常安装路径 @@ -29,15 +28,9 @@ Monitoring V2 for Windows 只能从最低是 `wins` v0.1.0 的 Windows 主机中 enabled: true as: c:\\etc\wmi-exporter\wmi-exporter.exe ``` - :::note 非默认 Windows 前缀路径的注意事项： - - - 如果你使用具有非默认 `win_prefix_path` 的 `cluster.yml` 来设置 RKE 集群，你需要将 `c:\\` 替换为你的前缀路径字段的值来修改 `masquerade.as`。 - - - 例如，如果你使用 `win_prefix_path: 'c:\host\opt\'`，则需要设置为 `as: c:\host\opt\etc\wmi-exporter\wmi-exporter.exe`。 - - ::: 2. 成功升级所有主机后，请再次使用默认值部署 Helm Chart，以避免与以下设置发生冲突： + ```yaml masquerade: enabled: false diff --git a/i18n/zh/docusaurus-plugin-content-docs/version-2.12/integrations-in-rancher/monitoring-and-alerting/windows-support.md b/i18n/zh/docusaurus-plugin-content-docs/version-2.12/integrations-in-rancher/monitoring-and-alerting/windows-support.md index c8de9476221..c46c0cc8f76 100644 --- a/i18n/zh/docusaurus-plugin-content-docs/version-2.12/integrations-in-rancher/monitoring-and-alerting/windows-support.md +++ b/i18n/zh/docusaurus-plugin-content-docs/version-2.12/integrations-in-rancher/monitoring-and-alerting/windows-support.md @@ -10,8 +10,6 @@ _从 v2.5.8 起可用_ Monitoring V2 for Windows 只能从最低是 `wins` v0.1.0 的 Windows 主机中抓取指标。要完全部署 Monitoring V2 for Windows，你的所有主机都必须满足此要求。 -如果你在 Rancher 2.5.8 中配置新的 RKE1 集群，你的集群应该已经满足此要求。 - ### 将现有集群升级到 wins v0.1.0 如果集群是在 Rancher 2.5.8 之前配置的（即使当前 Rancher 版本是 2.5.8），你将无法成功部署 Monitoring V2 for Windows，除非你将每台主机的 wins 版本升级到 v0.1.0 或以上版本。 @@ -19,6 +17,7 @@ Monitoring V2 for Windows 只能从最低是 `wins` v0.1.0 的 Windows 主机中 为了方便此次升级，Rancher 2.5.8 发布了一个全新的 Helm Chart，名为 `rancher-wins-upgrader`。 1. 使用以下覆盖部署 `rancher-wins-upgrader`： + ```yaml # 通过先前已列入白名单的进程路径 # 来引导 win-upgrader 安装，这是因为正常安装路径 @@ -29,15 +28,9 @@ Monitoring V2 for Windows 只能从最低是 `wins` v0.1.0 的 Windows 主机中 enabled: true as: c:\\etc\wmi-exporter\wmi-exporter.exe ``` - :::note 非默认 Windows 前缀路径的注意事项： - - - 如果你使用具有非默认 `win_prefix_path` 的 `cluster.yml` 来设置 RKE 集群，你需要将 `c:\\` 替换为你的前缀路径字段的值来修改 `masquerade.as`。 - - - 例如，如果你使用 `win_prefix_path: 'c:\host\opt\'`，则需要设置为 `as: c:\host\opt\etc\wmi-exporter\wmi-exporter.exe`。 - - ::: 2. 成功升级所有主机后，请再次使用默认值部署 Helm Chart，以避免与以下设置发生冲突： + ```yaml masquerade: enabled: false diff --git a/versioned_docs/version-2.12/integrations-in-rancher/monitoring-and-alerting/windows-support.md b/versioned_docs/version-2.12/integrations-in-rancher/monitoring-and-alerting/windows-support.md index 7f93c644ab2..db1dfb8bfa3 100644 --- a/versioned_docs/version-2.12/integrations-in-rancher/monitoring-and-alerting/windows-support.md +++ b/versioned_docs/version-2.12/integrations-in-rancher/monitoring-and-alerting/windows-support.md @@ -12,8 +12,6 @@ Monitoring V2 can be deployed on a Windows cluster to scrape metrics from Window Monitoring V2 for Windows can only scrape metrics from Windows hosts that have a minimum `wins` version of v0.1.0. To be able to fully deploy Monitoring V2 for Windows, all of your hosts must meet this requirement. -If you provision a fresh RKE1 cluster in Rancher 2.5.8, your cluster should already meet this requirement. - ### Upgrading Existing Clusters to wins v0.1.0 If the cluster was provisioned before Rancher 2.5.8 (even if the current Rancher version is 2.5.8), you will not be able to successfully deploy Monitoring V2 for Windows until you upgrade the wins version on each host to at least v0.1.0. @@ -21,6 +19,7 @@ If the cluster was provisioned before Rancher 2.5.8 (even if the current Rancher To facilitate this upgrade, Rancher 2.5.8 has released a brand new Helm chart called `rancher-wins-upgrader`. 1. Deploy `rancher-wins-upgrader` with the following override: + ```yaml # Masquerading bootstraps the wins-upgrader installation via # a previously whitelisted process path since the normal install path, @@ -31,15 +30,9 @@ To facilitate this upgrade, Rancher 2.5.8 has released a brand new Helm chart ca enabled: true as: c:\\etc\wmi-exporter\wmi-exporter.exe ``` - :::note Note for Non-Default Windows Prefix Path: - - - If you set up the RKE cluster with a `cluster.yml` that has a non-default `win_prefix_path`, you will need to update the `masquerade.as` field with your prefix path in place of `c:\\`. - - - For example, if you have `win_prefix_path: 'c:\host\opt\'`, then you will need to set `as: c:\host\opt\etc\wmi-exporter\wmi-exporter.exe`. - - ::: 2. Once all your hosts have been successfully upgraded, please ensure that you deploy the Helm chart once again with default values to avoid conflicts with the following settings: + ```yaml masquerade: enabled: false