catalog
catalog copied to clipboard
tektoncd
Decide strategy for hosting images used in catalog
- Where should they live (what registry)?
- Who rebuilds/maintains them?
- Where should the source/config live?
Are there IaaS resources we can get from sponsor companies through the CDF? We could host and maintain a public registry on the *.tekton.dev domain. That would give us a neutral home for the images.
As of now, we don't really have the resource power to maintain images so for now we should stick to relying on externaly maintained images.
Getting back on this a bit, I think, tektoncd/catalog shouldn't hold any code (including Dockerfile), except from it's own test-infra needs (makefiles, scripts, …).
Managing code release and overall lifecycle is gonna be extra work and a bit confusing in tektoncd/catalog. How to release just one part, when to tag a Dockerfile to a specific version, … All this is easier done in a separate repository (that groups or not the code themselves that make sense). The catalog should treat resources the same way, coming from tektoncd itself or not ; e.g. buildah or kaniko code and release lifecycle lives outside of tektoncd/catalog, it should be the same for git-init, …
This also simplifies the test-infra requirements / needs for the catalog : we test tasks that's all, we don't build code, we don't build images (at least none until we ship resource def as oci images).
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
/lifecycle stale
Send feedback to tektoncd/plumbing.
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
/close
Send feedback to tektoncd/plumbing.
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
/lifecycle rotten
Send feedback to tektoncd/plumbing.
@tekton-robot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity. Reopen the issue with
/reopen. Mark the issue as fresh with/remove-lifecycle rotten./close
Send feedback to tektoncd/plumbing.
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.
I think we still need to make some decisions here, particularly since we have tasks that now rely on pipelineresource images - if we phase out pipelineresources and/or completely change their designs, we're going to need to decide where to put them
@vdemeester and i put some thoughts in this doc
/lifecycle frozen
