Previously, we maintained OpenShift templates for deploying apps in development environments as well as delivering these templates to our customers for their on-prem deployment. Customers who refer to our templates (as well as documentation) have their own configuration management tools to automate the deployment such as ArgoCD and FluxCD.
My son's buildings |
Our developers usually modify templates (YAML) directly on OpenShift for testing and then adjust the corresponding templates stored in the Git repository in Bitbucket. This sometimes causes an issue that delivered templates are incorrect because:
- Developers forget to update the templates in Git repositories.
- Developers don’t test the templates
Therefore, our goal was to integrate a tool into our CI/CD that can automate and manage the configuration of OpenShift apps. The delivered templates should be the ones that are able to run on our OpenShift with the following purposes:
- Automate deployment from templated in Git repositories onto OpenShift
- Manage the configuration of the OpenShift apps. It should not allow modifying the configuration directly in OpenShift (as using an Operator Pod).
We found that adopting GitOps with FluxCD was a sufficient way to accomplish our goal.
---
References:
- GitOps
Comments
Post a Comment