Reduce the number of image we maintain here #1839
Labels
kind/misc
Categorizes issue or PR as a miscellaneuous one.
kind/question
Issues or PRs that are questions around the project or a particular feature
I wonder if we could reduce the number of images we maintain here to the minimum and rely more on upstream images instead. Few examples:
skopeo
has upstream images, and I am not even sure where it is used in our infrastructuretkn
could be managed directly ontektoncd/cli
, published at release time (and thus, having tagged version aligned with release)hub
is very similar to thisko
has an upstream image we could use as well I think (same, it would be tagged per version I think, cc @imjasonh)ko-gcloud
is a bit trickierkubectl
I am not sure, but it keels like there might be some official or semi-official / maintained image alreadyopenssh-server
is.. a wonder to me, not sure where / how we use that one evenI don't think it has a huge impact on cost (registry side), but, less things to maintain is less work 🙃 .
test-runner
is not really concerned as it is the image used byprow
, so it has everything in it. If we manage to get out of prow in the future, this image would become deprecated.cc @wlynch @afrittoli @tektoncd/plumbing-maintainers
(Sidenote: we could also migrate the one we can to
apko
maybe ?)The text was updated successfully, but these errors were encountered: