Harrison

Note that this fix is included in `103.1.1-rc1`, which means that rancher must be configured to deploy pre-release charts in order for this to be tested

Note that this fix is included in `104.0.0-rc1`, which means that rancher must be configured to deploy pre-release charts in order for this to be tested

This issue may be resolved now that https://github.com/rancher/rke2/issues/2204 has been validated in RKE2. This should be retested once RKE2 feb patches are available

We should retest this now that https://github.com/rancher/rke2/issues/5138 has been merged into RKE2 and validated, this issue should be retested as the linked RKE2 issue directly addresses the primary error described...

This can be tested, see https://github.com/rancher/rancher/issues/42783#issuecomment-1959703364 for more information

This can be tested, see https://github.com/rancher/rancher/issues/42783#issuecomment-1959703364 for more information

This PR is finally ready for review! After looking at `release/v2.9` I could not find a "released" `104` version of Rancher monitoring, so I've updated this PR to use version...

@adamkpickering Good catch! forgot I had done the same versioning change for the sub-chart as well. Should be fixed now

@jordojordo This fix doesn't seem to be present on 2.6-head, is there a way we can get it back ported? I'm unsure on how the UI team handles making fixes...

@gaktive This ticket is currently blocked by the respective UI work. rancher-machine has been updated so the required API schema changes should be present, resolving previous UI blockers.