search

tektoncd / catalog

Catalog of shared Tasks and Pipelines.
Apache License 2.0
666 stars 577 forks source link

Decide strategy for hosting images used in catalog #29

Open dlorenc opened 5 years ago

dlorenc commented 5 years ago
afrittoli commented 5 years ago

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.

vdemeester commented 5 years ago

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.

vdemeester commented 4 years ago

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, …

vdemeester commented 4 years ago

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).

tekton-robot commented 4 years ago

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.

tekton-robot commented 4 years ago

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.

tekton-robot commented 4 years ago

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 commented 4 years ago

@tekton-robot: Closing this issue.

In response to [this](https://github.com/tektoncd/catalog/issues/29#issuecomment-673894610): >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](https://github.com/tektoncd/plumbing). Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
bobcatfish commented 4 years ago

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