Brad Davidson
Brad Davidson
Will create k3s/rke2 issues to track the distro side of this. Rancher can add support once it's implemented in the distros.
See above linked issues for distro implementation. I'll leave this open pending integration on the rancher side.
I missed this again this cycle because it was Done :/ Rescheduling to next month.
I don't really want to get in the habit of bumping the version here in the checked-in manifest. If you want to use the manifest from git, use Kustomize to...
> When deploying in Airgap environments (using tarball installation), there is a tarball for the system-upgrade-controller image. However, we also need to include the kubectl image but the required version...
Huh, I guess that was added back in: * https://github.com/rancher/system-upgrade-controller/pull/26. I wasn't paying attention when that went in - I believe it was mostly done to make it easier to...
Yeah I guess for airgap environments we just kinda expect users to have an internal registry and a workflow to pull/push images into it, rather than using airgap images for...
What if it was just exclusive to nodes matching the selector? That is to say, what if exclusive plans were allowed to run at the same time as long as...
Actually I'm not sure any change is necessary. `exclusive` is implemented by a `PodAntiAffinity` on the Job Pod. All it does is prevent pods from different exclusive plans from running...
Yeah it shouldn't be possible to have an empty hash for a valid plan. That's an odd one for sure.