GitLab Multi Runner sets affinity and global at the same time
ikogan opened this issue · comments
The GitLab Multi Runner catalog entry seems to set io.rancher.scheduler.global: 'true' and, if you select an affinity, also sets io.rancher.scheduler.affinity:host_label: ${host_label} at the same time. This causes rancher/rancher#8129 and makes upgrading the stack impossible.