Summary
There is a list of mandatory chores that we need in each release, like testing Argo CD with the latest K8s version, upgrading the Go K8s client, Helm, Kustomize and more. Only some of those are handled by Renovate, and very partially.
We sometimes forget those chores in the release and as a result accrue tech debt.
Motivation
One example is that we are behind with upgrading to K8s client 0.35 simply because there was no direct owner of such an upgrade.
Proposal
I'd like to propose treating those chores as part of the release champion role and adding them to the release issue template, explaining they need to be worked on at the beginning of the release cycle.
Summary
There is a list of mandatory chores that we need in each release, like testing Argo CD with the latest K8s version, upgrading the Go K8s client, Helm, Kustomize and more. Only some of those are handled by Renovate, and very partially.
We sometimes forget those chores in the release and as a result accrue tech debt.
Motivation
One example is that we are behind with upgrading to K8s client 0.35 simply because there was no direct owner of such an upgrade.
Proposal
I'd like to propose treating those chores as part of the release champion role and adding them to the release issue template, explaining they need to be worked on at the beginning of the release cycle.