Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add factory support for pulling from k8s YAML in repo #9879

Closed
bmicklea opened this issue May 30, 2018 · 4 comments
Closed

Add factory support for pulling from k8s YAML in repo #9879

bmicklea opened this issue May 30, 2018 · 4 comments
Labels
kind/enhancement A feature request - must adhere to the feature request template. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. status/analyzing An issue has been proposed and it is currently being analyzed for effort and implementation approach

Comments

@bmicklea
Copy link

Description

Today we allow factories to optionally read runtime configuration from a dockerfile located in the repo. However, this only works with dockerfiles today.

We should offer a similar ability to have factories read the runtime configuration from a Kubernetes YAML in a repo when using Che on Kube or OpenShift.
@bmicklea bmicklea added kind/enhancement A feature request - must adhere to the feature request template. status/analyzing An issue has been proposed and it is currently being analyzed for effort and implementation approach labels May 30, 2018
@bmicklea
Copy link
Author

bmicklea commented May 30, 2018 •
edited
Loading

@slemeur and @eivantsov please update with additional details if needed.

@bmicklea bmicklea mentioned this issue May 30, 2018
Merged
@bmicklea
Copy link
Author

@benoitf your input here would be appreciated.

@slemeur
Copy link
Contributor

slemeur commented May 30, 2018

This is aligned with the requirements from workspace.next #8265

@gorkem gorkem mentioned this issue May 30, 2018
Closed
14 tasks
@che-bot
Copy link
Contributor

che-bot commented Sep 7, 2019

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.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 7, 2019
@che-bot che-bot closed this as completed Sep 17, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/enhancement A feature request - must adhere to the feature request template. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. status/analyzing An issue has been proposed and it is currently being analyzed for effort and implementation approach
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@slemeur @bmicklea @che-bot