search

eclipse-che / che

Kubernetes based Cloud Development Environments for Enterprise Teams
http://eclipse.org/che
Eclipse Public License 2.0
6.93k stars 1.19k forks source link

Provide pre-configured Camel K instance with Camel K stack #15391

Open apupier opened 4 years ago

apupier commented 4 years ago

Is your enhancement related to a problem? Please describe.

currently when using a Camel K stack, user need to have an already installed Camel instance somewhere or have enough rights to install it.

Describe the solution you'd like

when creating the workspace, a Camel K instance is available on whatever Kubernetes cluster it is installed on. It may require an action requested to an admin to install the Camel K Operator on the cluster.

Describe alternatives you've considered

when creating the workspace, a Camel K instance is available on whatever Kubernetes cluster it is installed on but it requires admin right if operator not available on the cluster.

As a first iteration, we can also imagine to have listed the requirements (installed operator) in the devfile and that Che is alerting user in case some of the operator is not available.

Additional context

might be done using Operator Lifecycle Manager if supported in devfile

follow-up on https://github.com/eclipse/che/issues/14831

l0rd commented 4 years ago

@apupier are you requesting the support for operators as a new component type in the devfile?

I believe that's something that we agreed last week we won't be able to support because it requires more privileges then we can grant to a Che user (privilege escalation).

apupier commented 4 years ago

we said that it won't be possible in short-term but that we might rely on Operator Lifecycle Manager in the future. It might need to request some rights to an admin but it should be integrated in a Kubernetes flow. And I wasn't precise enough in the "describe the solution you'd like", i will update

l0rd commented 4 years ago

yeah we agreed that we would like to support Kubernetes Custom Resources, but CRD need to be deployed beforehand.

che-bot commented 4 years ago

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.

apupier commented 4 years ago

it stays something interesting to have in the future

apupier commented 4 years ago

/remove-lifecycle stale

che-bot commented 3 years ago

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.