Kyverno uses a number of container images that we would want to cache in our container registry, to don't rely on external infrastructure being online for us to deploy our stuff.
This is similar to what we do with ingress-nginx
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T362869 [k8s,infra] Upgrade Toolforge to Uwubernetes (1.30) | |||
| Open | None | T362868 [infra,k8s] Upgrade Toolforge Kubernetes to version 1.29 | |||
| Open | None | T362867 [infra,k8s] Upgrade Toolforge Kubernetes to version 1.28 | |||
| Open | None | T359641 [infra,k8s] Upgrade Toolforge Kubernetes to version 1.27 | |||
| Open | None | T327025 [infra,k8s] Upgrade Toolforge Kubernetes to version 1.26 | |||
| Open | None | T316107 [infra,k8s] Upgrade Toolforge Kubernetes to version 1.25 | |||
| In Progress | aborrero | T279110 [infra] Replace PodSecurityPolicy in Toolforge Kubernetes | |||
| Open | aborrero | T364113 toolforge: identify and cache in our container registry all kyverno images |