Cloud & DevOps / Infrastructure blueprint

Thabit Control Plane

A GitOps control-plane blueprint for reviewed infrastructure changes, application reconciliation, drift detection, and rollback automation.

Explore the architecture ↓View repository ↗
Focus
Infrastructure & platform engineering
Project type
Infrastructure blueprint
Core technologies
Terraform · Atlantis · Argo CD · EKS
Thabit Control Plane concept interface illustration
Concept interface illustration

Context

The engineering problem

Manual infrastructure edits create a gap between declared configuration and running systems. Teams need reviewable changes and a deliberate response to drift.

System architecture

Architecture at a glance

A simplified map of the intended relationships in this blueprint. Integration gaps are described in the implementation scope; arrows do not establish a running deployment.

  1. clientGit pull request
    Review workflow
    gatewayAtlantis / policy
  2. gatewayAtlantis / policy
    Plan / apply
    infraTerraform resources
  3. clientGit pull request
    Desired application state
    serviceArgo CD
  4. serviceArgo CD
    Reconcile
    serviceEKS workloads
  5. infraTerraform resources
    State inspection
    infraDrift / rollback
All system components (6)
  • Git pull requestclient
  • Atlantis / policygateway
  • Terraform resourcesinfra
  • Argo CDservice
  • EKS workloadsservice
  • Drift / rollbackinfra

Approach

Implementation decisions

  • Terraform
  • Atlantis
  • Argo CD
  • EKS
  • OPA
  • Kyverno
  • Python

Review infrastructure changes

Atlantis workflow configuration provides a pull-request path for Terraform plans and applies.

Declare application state

Argo CD, ApplicationSet, and secret-management modules keep desired deployment state in versioned configuration.

Make recovery inspectable

Resource-existence checks and recovery scripts make the proposed operational workflow reviewable. A missing-resource alert and an attribute-level drift comparison are different checks.

Explore the implementation

Start with the source.

These entry points connect the architecture to the implementation.

Implementation scope

GitOps infrastructure and automation reference. The detector checks whether selected resources exist; it does not compare all resource attributes. Production recovery alerts an operator, and the optional staging rollback path requires correction and testing before use.