Pipeline: Proposal: Add a default "image" for script mode
This would allow users to simplify yaml even further with script mode. Right now we require them to specify an image, but Tekton could default to something reasonable.
dlorenc
All 11 comments
/kind feature
/cc @ImJasonH
vdemeester
on 4 Dec 2019
Questions we'd need to answer:
- what shells or scripting environments should be included?
- if platform providers can change the default image, what tools (at what versions) must be included to be considered compliant?
- what's the base OS we should use by default and what traits of it should we require of other non-default platform provided overrides?
- what's the versioning story for upgrading the version of whatever tools are available in the image?
ImJasonH
on 4 Dec 2019
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
on 13 Aug 2020
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
on 13 Aug 2020
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
on 13 Aug 2020
@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.
tekton-robot
on 13 Aug 2020
/remove-lifecycle rotten
/remove-lifecycle stale
/reopen
vdemeester
on 13 Aug 2020
@vdemeester: Reopened this issue.
In response to this:
/remove-lifecycle rotten
/remove-lifecycle stale
/reopen
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.
tekton-robot
on 13 Aug 2020
Marking this for triage to get a sense from other OWNERS if we want this or not
bobcatfish
on 1 Sep 2020
This sounds tempting, but the questions in https://github.com/tektoncd/pipeline/issues/1676#issuecomment-561627587 (and likely more we'd uncover) make me think it's not worth jumping in to. Allowing operators or providers to configure their own defaults might also harm portability (script on platform A works because its default script image has ls with some flag, but breaks on platform B because its ls doesn't support that flag or something)
So ultimately I'm mildly -1 on it.
ImJasonH
on 2 Sep 2020
/close
Given the open questions above, and a general feeling that we'd need to provide lots of tools baked in to the image which we can't really predict in advance, I'm going to close this for now unless a really strong use case rears its head in future.
sbwsg
on 5 Oct 2020
Related issues
cnych
·
4Comments
vdemeester
·
3Comments
csantanapr
·
3Comments
sbwsg
·
4Comments
sujithjoseph
·
3Comments
Most helpful comment
This sounds tempting, but the questions in https://github.com/tektoncd/pipeline/issues/1676#issuecomment-561627587 (and likely more we'd uncover) make me think it's not worth jumping in to. Allowing operators or providers to configure their own defaults might also harm portability (
scripton platform A works because its default script image haslswith some flag, but breaks on platform B because itslsdoesn't support that flag or something)So ultimately I'm mildly -1 on it.