Fabric8 on OpenShift vs on Kubernetes

Krzysztof Sobkowiak

unread,

Mar 26, 2017, 3:42:28 PM3/26/17

to fabric8

Hi

Do you see any benefits when using Fabric8 on OpenShift over using it on vanilla Kubernetes? As far as I know Fabric8 uses Kubernetes interface. So my question whether there is any added value to use it on OpenShift.

Kindly regards
Krzysztof

--
Krzysztof Sobkowiak (@ksobkowiak)

JEE & OSS Architect, Integration Architect
Apache Software Foundation Member (http://apache.org/)
Apache ServiceMix Committer & PMC Member (http://servicemix.apache.org/)
Senior Solution Architect @ Capgemini SSC (http://www.capgeminisoftware.pl/)

James Strachan

unread,

Mar 27, 2017, 3:14:32 AM3/27/17

to Krzysztof Sobkowiak, fabric8

OpenShift is Red Hat's distribution of Kubernetes; so they are intentionally quite similar. The main difference is OpenShift adds OAuth & RBAC and a number of security features (e.g. avoiding the exposing of the docker socket which many see as a security issue) plus you can get commercial support for OpenShift together with the underlying operating systems, images and middleware.

--
You received this message because you are subscribed to the Google Groups "fabric8" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fabric8+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

James
-------
Red Hat

Twitter: @jstrachan
Email: james.s...@gmail.com

Blog: https://medium.com/@jstrachan/

fabric8: https://fabric8.io/

open source development platform

funktion: https://funktion.fabric8.io/

open source event based lambda programming

Sobkowiak Krzysztof

unread,

Mar 27, 2017, 4:30:04 AM3/27/17

to fabric8

But from the fabric8 side there is no difference? It has the same functionalities, no matter whether deployed on OpenShift or Kubernetes?

On 27.03.2017 09:14, James Strachan wrote:

OpenShift is Red Hat's distribution of Kubernetes; so they are intentionally quite similar. The main difference is OpenShift adds OAuth & RBAC and a number of security features (e.g. avoiding the exposing of the docker socket which many see as a security issue) plus you can get commercial support for OpenShift together with the underlying operating systems, images and middleware.

On 26 March 2017 at 20:42, Krzysztof Sobkowiak <krzys.s...@gmail.com> wrote:

Hi

Do you see any benefits when using Fabric8 on OpenShift over using it on vanilla Kubernetes? As far as I know Fabric8 uses Kubernetes interface. So my question whether there is any added value to use it on OpenShift.

Kindly regards
Krzysztof

--

James
-------
Red Hat

Twitter: @jstrachan
Email: james.s...@gmail.com

Blog: https://medium.com/@jstrachan/

fabric8: https://fabric8.io/

open source development platform

funktion: https://funktion.fabric8.io/

open source event based lambda programming

--
Krzysztof Sobkowiak

James Strachan

unread,

Mar 27, 2017, 4:34:27 AM3/27/17

to Sobkowiak Krzysztof, fabric8

The main difference is when deployed on OpenShift then fabric8 will default to using OpenShift S2I binary builds so it won't need access to the docker socket. Also Jenkins Jobs and Builds get sync'd to OpenShift BuildConfig and Build resources so that you can view them with the `oc` CLI. So there are differences; but they are very similar.

--

You received this message because you are subscribed to the Google Groups "fabric8" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fabric8+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply all

Reply to author

Forward