[oso2k]

Disclaimer: I work as a Red Hat Consulting Architect focused on OpenShift (our Kubernetes distro).

I didn’t say anything about being a genius or being stupid. But it does help to have some something to reference [0][1].

In short, there’s several things that help.

   1) Start with 3 Master nodes that sit behind an Enterprise Load Balancer (or even HAProxy) and a VIP (console.example.com)
   2) We choose to have 3 Infrastructure nodes that perform Container load balancing (app routers), log aggregation, metrics collection, and registry hosting
   3) We then put another VIP and Load Balancer in front of Application Subdomain (*.apps.example.com) so that apps can be exposed outside the cluster (myjavaapp.apps.example.com)
   4) Stand up 3 or more worker nodes

Yes. This is more complex than plain old Containers. Yes. This is harder than putting an Apache server with RoR and MariaDB on the same Linux VM. But there is lots of value there if you put in the effort. Lots of consultants run “all-in-one” VMs or minishift/minikube On their laptops or homelabs.

[0] http://uncontained.io/articles/openshift-ha-installation/

[1] https://docs.openshift.com/container-platform/3.11/install/i...

[zebraflask]

This makes sense to me. I'm going to give it a whirl.