You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@edward-bear it is possible to use the Helm chart in your situation.
The wins-upgrader Helm chart cannot be used to upgrade to older versions of wins (e.g. upgrade 0.0.3 to 0.0.4) since the newer version of wins you are planning to upgrade to should be v1.0.0+ (as it must support ./wins upgrade to perform the upgrade).
However, upgrading from an older version of wins like 0.0.4 to wins 1.0.0+ should be supported since we only rely on the existing wins server having the capability to run the upgrade command on the provided wins binary.
The reason why this isn’t explicitly called out in the README is because upgrading from 0.4.0 to 1.0.0+ is a special exception, as in most situations you will have to turn on masquerading to get wins deployed (which is a special process, as noted in the README).
However, I’d be open to updating the README to clarify this requirement.
Hello All,
Please help and clarify this requirement.
Most of us have probably come to this helm chart via:
https://rancher.com/docs/rancher/v2.5/en/monitoring-alerting/windows-clusters/#cluster-requirements
And the need to upgrade to a wins version >= v0.1.0.
The helm Readme requirements state:
"A Windows Service called rancher-wins is currently running on each Windows host that is running a wins server version of v0.1.0+."
I have a wins version of 0.0.4 running on my nodes.. so please confirm if it's possible for me to use this Helm chart or not.
Thank you
The text was updated successfully, but these errors were encountered: