[RFE] More control over rancher/webhook updates

[frankbou]

When we update Rancher and Kubernetes version on a large number of downstream clusters, that change must pass through internal validation steps (automatic tests, manual tests, deployment plan, approvals, etc...).

For us, the main benefit of using Rancher + RKE instead of using a managed Kubernetes service offered by a cloud provider is to have control on what is deployed on our environments and to have more control on when these deployments are done.

We are used to controlling Rancher and Kubernetes updates.

We don't understand how rancher-webhook has been updated to 0.3.4 last night without allowing us to test and approve that change. We didn't find documentation on that automatic update process.

We would like to have more control over the release process of rancher-webhook.
From my point of view (i'm a rancher user), I would expect rancher-webhook to be updated at the same time as Rancher.

Would it be possible to link webhook releases to Rancher ones ?
E.g. : The update of rancher 3.7.5 would trigger the rancher-webhook 0.3.6 update.

Optionally, we would be able to force a specific version of the rancher-webhook without updating Rancher (to be able to push a hotfix of rancher-webhook quickly if needed).

[frankbou]

i close this issue because it is duplicated
rancher/rancher#40159
PR : rancher/rancher#41302