eclipse-che
Support inner loop image components
Is your enhancement related to a problem? Please describe
Che currently ignores image components. But, if autobuild:true, an image component should be build at startup and available as the image of other containers/kubernetes components. An example would be the dev tooling container that could be defined by a Dockerfile that lives in the git repo, close to the application source code and to the Devfile.
Describe the solution you'd like
Support the auto-build: through tekton, s2i etc… Pause the workspace startup until the image has been built Support the usage of the “just-built” image by a container/kubernetes component that references it: use local registries (openshift has its own one, minikube has a add-on to include it…)
Describe alternatives you've considered
No response
Additional context
No response
Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.
Mark the issue as fresh with /remove-lifecycle stale in a new comment.
If this issue is safe to close now please do so.
Moderators: Add lifecycle/frozen label to avoid stale mode.
Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.
Mark the issue as fresh with /remove-lifecycle stale in a new comment.
If this issue is safe to close now please do so.
Moderators: Add lifecycle/frozen label to avoid stale mode.