GitOps for organizations: provisioning and configuring OpenShift clusters automatically

When the organizations started to adopt Kubernetes platforms, like OpenShift, many years ago, the most common scenario was a single cluster for all the workloads. However, as the rate of OpenShift adoption got faster inside the organizations, more clusters were needed. And each organization started to work on its own automation: some of them used Ansible for the provisioning, others Terraform. Some of them used Ansible for the Day2 configuration and Cluster Life Cycle, others used GitOps tools like ArgoCD or Drone. Implementing the whole workflow of provisioning, day 2 configuration and Cluster Life Cycle in an automated way is not a simple task, and as there are no standards, each team defines its own solution.

In this article, I’ll not just describe how to create the whole workflow of Provisioning, Day 2 configuration and Cluster Lifecycle; but I’ll do it from an enterprise perspective. And this is the most important part of this article: I’m not using any cool custom plugin, or an amazing tool just found in GitHub. Don’t get me wrong, I love to try new tools, but organizations require tools which are supported, used by other companies, coming from a reliable source.

“GitOps for organizations” is a solution for provisioning and configuring OpenShift clusters using Red Hat products (ACM and OpenShift Gitops), allowing the use of any orchestrator (AAP/Tower, Service Now, Jenkins…). In this solution, git is the central integration point and the source of truth. ACM will be used for provisioning and applying policies, and OpenShift Gitops (ArgoCD) as Continuous Delivery tool for applying all the configuration to all out OpenShift clusters.

Continue reading:

Author avatar