Skip to Content
Skip Breadcrumb

Tag: openshift

The main reason why this blog post exist is that OpenShift V3 and Kubernetes is very close binded to port 8443. This could be changed in the future.

UPDATE: Since OpenShift Enterprise 3.4 are both ports openshift_master_api_port and openshift_master_console_port documented Configuring Master API and Console Ports.

I used several times a dedicated haproxy pod to provide access to the OpenShift v3 Web console and api on port 443 (https).

This concept could also be used for different services in the PaaS which are able to talk via SNI.

There is now a description on the rhcloud how to create a custom role in openshift. Custom Role Creationtl;dr The required steps. export # oc export clusterrole edit > customrole.yaml # vi customrole.yaml edit change name: edit_without_rsh remove unwanted resources and verbs save file create # oc create -f clusterrole.yaml # oc adm policy add-role-to-user edit_without_rsh <username> -n <project> You can contact me for any further questions and orders
I have now created a docker image and pushed it on docker hub, based on my post How to use haproxy 1.7 in openshift router openshift-origin-router-hap17You can use this image as image parameter as described in the doc Using a Different Router Image. For example. oc adm router region-west -o yaml \ --images=me2digital/openshift-origin-router-hap17:latest \ --credentials=${ROUTER_KUBECONFIG:-$KUBECONFIG} \ --service-account=router You can contact me for any further questions and orders

The current openshift router images uses the Red Hat RPM package of haproxy. This package is maintained by Red Hat and uses haproxy 1.5 with some Red Hat patches.

You can see what’s in the package on centos git repo

It’s not bad but haproxy have now released the version 1.7.x, therefore there are several enhancements and bugfixes in the newer versions.

Changelog 1.6
Changelog 1.7