Tag: kubernetes

I use the excellent service from Beamy-Lake to have my own Nextcloud and ejabberd instance. As I travel a lot I faced the problem that in some WIFI’s some ports are forbidden for outgoing communication 😱. The solution is to use a Software which can handle TCP and HTTP via port 443 so that I can use my nextcloud and my jabber client on the same port.

A lot of enterprise applications are not yet cloud-ready or even designed as micro-services. Due to this fact, session stickiness is required for a lot of the enterprise Applications.
Let me explain how OpenShift Enterprise (= OCP) and origin can help you solve this topic for you.

A lot of OpenShift user want to use more external available ports to reach Applications inside a OpenShift cluster then 80 or 443. I describe here how you can setup a so called ingress port and some pitfalls which could happen and how you can prevent these.

A lot of enterprise companies have there own CA and PKI . The main issue on a own Cloud Infrastructure like kubernetes and openshift is to distribute the CA on every machine.

As you can read in my blog post about syslog in a container world it isn’t easy to run a syslogger in a none privileged Container which is the default setup on openshift.

I describe here how you can setup a syslog receiver for the openshift router which is possible since the version 3.3 via Router Environment Variables.