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 Secret object in Kubernetes/OpenShift recipe #11508

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

Support Secret object in Kubernetes/OpenShift recipe #11508

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/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it.

Comments

@sleshchenko
Copy link
Member

Description

A using of Secret is a very common way to store application credentials. But Eclipse Che ignores Secrets which are specified in Kubernetes/OpenShift recipe which leads to workspace start failing if there is any Pod/ConfigMap which references it.
It is needed to support Secret object in Kubernetes/OpenShift recipe.
The only one issue that should be decided - should we create Secret with an original name, or rename it to a random one (with fixing references in Pods, ConfigMaps) to avoid collisions if two or more workspaces are run in the same namespace/project.
@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
@slemeur slemeur mentioned this issue Dec 11, 2018
Closed
69 tasks
@ibuziuk ibuziuk mentioned this issue Dec 20, 2018
Closed
@amisevsk amisevsk mentioned this issue Jan 22, 2019
Merged
@amisevsk
Copy link
Contributor

amisevsk commented Feb 1, 2019

Added in #12486

@amisevsk amisevsk closed this as completed Feb 1, 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/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@sleshchenko @amisevsk