Research different ways to handle cri-tools and kubernetes-cni packages

[xmudrii]

We have a dedicated repository for each Kubernetes minor release. However, some packages, such as kubernetes-cni, are not versioned in the same way as Kubernetes. That said, kubernetes-cni 1.2.0 might exist in different repositories.

We want to save on storage, build time, and maintenance, so we want to try to find a way to build and maintain kubernetes-cni in a single repository, but publish it in multiple repositories.

This should be figured out before putting OBS in the production to avoid making changes to the setup after end users start using it.

/assign
/sig release
/area release-eng
/priority critical-urgent

[xmudrii]

This is done and will be documented as part of kubernetes/sig-release#2289
/close

[k8s-ci-robot]

@xmudrii: Closing this issue.

In response to this:

This is done and will be documented as part of kubernetes/sig-release#2289
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.