New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OpenShift deployment documentation #403

vorburger opened this Issue Mar 5, 2018 · 2 comments


None yet
2 participants

vorburger commented Mar 5, 2018

The current documentation about how to deploy on OpenShift seems to be for OpenShift v2 (its old pre-Kubernetes based version), and was GUI screenshot instead of automatable CLI based.

It would be cool to have documentation showing how can be deployed to OpenShift v3 (like the public cloud on, or locally on minishift for development). It would also be a cool OpenShift show case... ;-)

I have made a start with exploring that this weekend, see master...vorburger:openshift... it's still very much WIP, incomplete (thus no PR, yet) - but I thought I would already share this here anyway... ;) Will update this when usable!


This comment has been minimized.


syjer commented Mar 5, 2018

hi @vorburger, thank you for doing the update, we were discussing about it recently :)

By the way, if you want, you can also submit a PR for the website too :) (


This comment has been minimized.


vorburger commented Oct 2, 2018

I now have this fully running (using 1.x-maintenance and no longer master, following the hint in #511), see 1.x-maintenance...vorburger:openshift_1.x-maintenance ... just cleaned it all up now, and raised (a first) PR #524!

Here's some gaps that I will leave open for some future additional contribution (from me or anyone else wanting to help with this):

  • add suitable Readiness & Liveness Probes healthcheckes to both (Actuator) & PostgreSQL
  • use a Template, pwd as arg
  • use a secret for the password
  • monitoring for both JVM, Spring Boot tracing and PostgreSQL performance & health
  • rename the postgresql-95-centos7 service
  • make it trigger a (first) build automatically on apply
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment