Deploying HealthShare/Ensemble Container on OpenShift

Primary tabs

Hello!

Checking to see if anyone has experience with deploying their Docker containers on a platform like OpenShift (or vanilla Kubernetes)?

If you have, do you have any guidance or lessons-learned?  Is this even something feasible with a HealthShare/Ensemble instance?

Answers

I have configured automatic deployment of the application to Kubernetes with Helm from GitLab as a part of CI/CD process.

I would not say that I had some specific issues, just well configured Kubernetes cluster with the right storage driver. Any InterSystems products supports devicemapper and aufs right now, yet. So, of course, better to have devicemapper available server, and use this possibility. AUFS already deprecated by Docker and will disappear in the next major release.

Hello,

Any idea how to onbaord the IRIS or ensemble / health share on openshift. There is tar IRIS_Community-2019.4.0.379.0-dockerubuntux64.tar.gz for ubuntu. Will be great for any reference.

You can deploy IRIS with Kubernetes which is inside of OpenShift. It is not so easy to explain here. As it will be just a common task, rather than something narrow just for you. Deploying a database to the cluster is a very specific task, and very depends on your needs.

As well as Kubernetes, I think you may also use ICM, did not use it before, so, not sure if it will work with OpenShift as well.

Thanks a lot, without the ICM, the docker version is working on Open shift. however on the interoperability part, there is no name space is blank as the per screen. is it some thing we need to patch or available in ICM. Key objective is to have the iris including ensemble and healthshare on openshift .

It's just a default empty instance. You then have to create a new namespace with the database. Interoperability will be enabled by default in that new Namespace, and it will appear there. But, you should have in mind, that all those changes may disappear by default, when you delete your container and start it again, it will be the same as in the first start. You can configure durable %SYS, to get it stored outside of the container or volumes.