David Ko
David Ko
cc @PhanLe1010 we allow users to install in a hybrid cluster but users need to use node selector to skip installing longhorn components on it. https://longhorn.io/docs/1.2.4/advanced-resources/deploy/rancher_windows_cluster/
> This was a found in a test case from [this](https://github.com/rancher/dashboard/issues/5137) issue for allowing installation of charts in hybrid clusters without the need for setting tolerations/node-selectors manually. Sounds like this...
Let's fix this in the upcoming 1.3.1 and 1.2.5. - Add `permit-os` as @PennyScissors mentioned - Add the default toleration and node selector (@PennyScissors mentioned) for user-deployed components (Manager, Driver,...
This has been improved in upcoming Longhorn 1.4.0, 1.3.1, and 1.2.5. We will update the corresponding Rancher chart for 1.3.1 to resolve this issue because 1.3.1 is the first upcoming...
> @innobead Since the Rancher chart for 1.3.1 has been released already - can this now be moved to-test for v2.6.9? Yes, please.
You encountered a known issue if using Longhorn from 1.0. Check the workaround at https://github.com/longhorn/longhorn/issues/4340#issuecomment-1201287027 for 1.3.0, and this has been fixed in 1.3.1. cc @derekbit
> We need to convert `""` to `disabled` in the conversion webhook. v1.0 does not have the dataLocality parameter, and the value is not handled in the upgrade path (v1.0->v1.1...
ref: https://github.com/longhorn/longhorn/issues/4210
This needs @longhorn/qa to update upgrade testing engine image. cc @chriscchien