Solution Pattern: Name Template

Architecture

Introduction for the architecture of this solution pattern.

1. Common Challenges

Most existing processes for infrastructure, configuration & deployment management face challenges like failed deployments, poor infrastructure design etc. Some of the common challenges are:

  • Configuration inconsistency in environments: It is difficult to track whether desired and actual configuration of an environment match. With manual changes being done, configuration drift will exist in the environment.

  • No development history of applications: It is difficult to find out how applications were built and deployed initially and who worked on them.

  • Security holes in environments: These holes were created for the sake of easier admin access to Continuous Delivery tools. These holes ensure velocity and convenience of development but endanger both applications and their users.

  • Difficulties of disaster recovery: With manual/half-manual processes, disaster recovery requires a strategy in place, which isn’t always upto date.

Fortunately, the GitOps approach can help us resolve all of these issues, provided its principles are properly implemented.

In addition to the above challenges, we could also face security attacks if vulnerable images are being used from Public Container Images.

RedHat ODF can be used to create private Red Hat Quay registry, a distributed and highly available container image registry for the enterprise. Quay provides secure storage, distribution and governance of containers and cloud-native artifacts on any infrastructure.

3. An in-depth look at the solution’s architecture

This solution has a Hub Cluster or Management Hub which manages all the other managed clusters. Hub Cluster has ArgoCD deployed in it, which in turns deploys different applications such as RedHat ACM, Vault etc. We can create new or import existing Openshift clusters through RedHat ACM.

architecture

MultiCloud GitOps with ODF & Quay: ODF is being installed on Hub and Managed clusters as an ArgoCD application. We can configure ODF installation on each cluster as per the requirements. Once ODF is installed on Hub Cluster, RedHat Quay is also deployed which is using RedHat ODF as the backend. RedHat Quay is a distributed and highly available container image registry.

MultiCloudODF