Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [che-dev] The future of Docker Infrastructure
Hi Brian,

Yes of course. Everything about Che development should stay on this mailing list. As well as on other channels: mattermost and the community call that happen every two weeks.

Another thing worth mentioning is that the source code for all infrastructures support is and will stay on the same GitHub repository (eclipse/che).

Mario

Il giorno mar 6 nov 2018, 08:58 Brian Dube <brian@xxxxxxxxxxx> ha scritto:
Hi Mario,

Thanks for this update. Will discussions for Docker support stay on this mailing list or will they eventually transition elsewhere? I guess I have the same question for code repositories and other infrastructure, too.

Brian

On Mon, Nov 5, 2018 at 11:00 PM Mario <mario.loriedo@xxxxxxxxx> wrote:

Hello all,


## Focusing on Kubernetes

We currently support deploying Che on Docker, Kubernetes and OpenShift. Considered that Kubernetes and OpenShift are more suited to run Che in production, that kube popularity has skyrocketed in the last couple of years and that supporting both Kubernetes and Docker infrastructures is resource consuming, we (Red Hat) are considering progressively disengaging on maintaining Docker based Che. In particular we will stop maintaining it with the release of Che 7 that will happen in first half of 2019.


## What will happen to Docker infrastructure?

Our engineers have worked hard to build the current Che Docker infrastructure and Docker may still be an interesting platform for deploying Che. So, even if Red Hat will focus on Kubernetes/OpenShift, we are looking for some contributors or organizations that would be interested in taking over this responsibility. We would be more than happy to work with whoever want to maintain Docker infrastructure to make the transition possible.


## What does maintaining the Docker infrastructure mean?

Maintainers should consider at least the following tasks:

  • In the short term: implementing Che 7 newest abstractions (plugin, editor, broker, jwt proxy)

  • In the longer term: running the CI to test Docker infrastructure

  • Recurring: updating the Docker client to support newer versions of the Docker API


Mario


_______________________________________________
che-dev mailing list
che-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/che-dev
_______________________________________________
che-dev mailing list
che-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/che-dev

Back to the top