Skip to content

Reduce the number of image we maintain here #1839

Open
@vdemeester

Description

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 infrastructure
  • tkn could be managed directly on tektoncd/cli, published at release time (and thus, having tagged version aligned with release)
  • hub is very similar to this
  • ko 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 trickier
  • kubectl I am not sure, but it keels like there might be some official or semi-official / maintained image already
  • openssh-server is.. a wonder to me, not sure where / how we use that one even

I 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 by prow, 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 ?)

Metadata

Assignees

No one assigned

    Labels

    kind/miscCategorizes issue or PR as a miscellaneuous one.kind/questionIssues or PRs that are questions around the project or a particular feature

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions