Re: [che-dev] Using internal network for che-services back-ends by defau

[Mykola Morhun <mmorhun@xxxxxxxxxx>]

I think we should have it turned on by default. That would allow us to avoid some network related issues and make Che work in a wider number of environments out of the box.

On Tue, Nov 10, 2020 at 10:39 AM Anatolii Bazko <abazko@xxxxxxxxxx> wrote:

Hello.

My personal opinion:
  - enable this feature by default and allow users to turn that off using the field in the CR.

  - to have it backward compatible: updating to a newer version shouldn't turn this feature on.

On Tue, Nov 10, 2020 at 2:19 AM Oleksandr Andriienko <oandriie@xxxxxxxxxx> wrote:

Hello. We have an issue about using an internal cluster network in the Che services: https://github.com/eclipse/che/issues/17644. Few words about this feature: it should resolve some network issues related to proxy, firewalls and so on, and it should improve Che performance, because internal network requests usually have a better ping than requests to the public hostname url. We implemented this feature for che-operator installer and it's an optional. Users can enable/disable it using Custom Resource org.eclipse.CheCluster.
We prepared pr's with implementation of this feature:

https://github.com/eclipse/che/pull/17945
https://github.com/eclipse/che/pull/18225
https://github.com/eclipse/che-operator/pull/468
https://github.com/eclipse/che-operator/pull/507

In the frame of this issue, we want to discuss if this feature should be enabled/disabled by default. So, if you want, share your opinion, please.

_______________________________________________
che-dev mailing list
che-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/che-dev

--

ANATOLII BAZKO

PRINCIPAL DEVELOPER

Red Hat Ukraine

_______________________________________________
che-dev mailing list
che-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/che-dev

--

Mykola Morhun

Software engineer

Red Hat