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

Support ConfigMap object in Kubernetes/OpenShift recipe #11507

Closed
sleshchenko opened this issue Oct 5, 2018 · 1 comment
Closed

Support ConfigMap object in Kubernetes/OpenShift recipe #11507

sleshchenko opened this issue Oct 5, 2018 · 1 comment
Assignees
@amisevsk
Labels
kind/enhancement A feature request - must adhere to the feature request template. status/code-review This issue has a pull request posted for it and is awaiting code review completion by the community.

Comments

@sleshchenko
Copy link
Member

sleshchenko commented Oct 5, 2018 •
edited
Loading

Description

A using of ConfigMap is a very common way to store application configuration. But Eclipse Che ignores ConfigMaps which are specified in Kubernetes/OpenShift recipe which leads to workspace start failing if there is any Pod which references it.
It is needed to support ConfigMap object in Kubernetes/OpenShift recipe.
The only one issue that should be decided - should we create ConfigMap with an original name, or rename it to a random one (with fixing references in Pods) to avoid collisions if two or more workspaces are run in the same namespace/project.

Reproduction Steps

OS and version:

Diagnostics:
@sleshchenko sleshchenko added kind/enhancement A feature request - must adhere to the feature request template. status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it. team/platform labels Oct 5, 2018
@sleshchenko sleshchenko mentioned this issue Oct 5, 2018
Closed
@ibuziuk ibuziuk mentioned this issue Dec 5, 2018
Closed
@amisevsk amisevsk self-assigned this Dec 7, 2018
@slemeur slemeur mentioned this issue Dec 11, 2018
Closed
69 tasks
@amisevsk amisevsk mentioned this issue Dec 17, 2018
Merged
@sleshchenko sleshchenko added status/code-review This issue has a pull request posted for it and is awaiting code review completion by the community. and removed status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it. labels Dec 17, 2018
@amisevsk amisevsk mentioned this issue Dec 21, 2018
Merged
@ibuziuk
Copy link
Member

ibuziuk commented Jan 9, 2019

@amisevsk I believe we can close it now

@ibuziuk ibuziuk closed this as completed Jan 9, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@amisevsk amisevsk

Labels
kind/enhancement A feature request - must adhere to the feature request template. status/code-review This issue has a pull request posted for it and is awaiting code review completion by the community.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@ibuziuk @sleshchenko @amisevsk