public/rancher-docs
1
0
Fork 0
mirror of https://github.com/rancher/rancher-docs.git synced 2026-09-25 04:28:15 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #1954 from LucasSaintarbor/rke1-removal-integrations-in-rancher-pt2

Browse Source 
Remove RKE1: /integrations-in-rancher pages Part 2
This commit is contained in:
Billy Tat
2025-08-21 13:19:20 -07:00
committed by GitHub
parent f6b53affe0 d23aff28d8
commit 1ac6e81329
8 changed files with 8 additions and 44 deletions
Download Patch File Download Diff File Expand all files Collapse all files
versioned_docs/version-2.12/integrations-in-rancher/monitoring-and-alerting/monitoring-and-alerting.md
-2
View File
@@ -91,8 +91,6 @@ For more information on `rancher-monitoring` chart options, including options to
## Windows Cluster Support
When deployed onto an RKE1 Windows cluster, Monitoring V2 will now automatically deploy a [windows-exporter](https://github.com/prometheus-community/windows_exporter) DaemonSet and set up a ServiceMonitor to collect metrics from each of the deployed Pods. This will populate Prometheus with `windows_` metrics that are akin to the `node_` metrics exported by [node_exporter](https://github.com/prometheus/node_exporter) for Linux hosts.
To be able to fully deploy Monitoring V2 for Windows, all of your Windows hosts must have a minimum [wins](https://github.com/rancher/wins) version of v0.1.0.
For more details on how to upgrade wins on existing Windows hosts, see [Windows cluster support for Monitoring V2.](windows-support.md).
versioned_docs/version-2.12/integrations-in-rancher/monitoring-and-alerting/windows-support.md
+2 -9
View File
@@ -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