31 July 2019
When deploying applications with container orchestrators such as Kubernetes or OpenShift, the need for templating is rapidly felt. Indeed it is the way to easily:
- manage several environments (staging, pre-prod, production…)
- manage similar logical groups of resources (configmap, deployment, service, route…)
On Kubernetes, the usual first choice is Helm even though several alternatives exist. However, when it comes to OpenShift, the choice is somehow trickier because there is a native OpenShift resource for templating. On one hand, this resource is rather basic in terms of functionalities. But on the other hand, the installation of Tiller on OpenShift means giving it the edit (or admin in some cases) rights on all your projects. Thus, it means lower security standards of your OpenShift projects. So what should you choose?