Skip to content

control plane

3 posts with the tag “control plane”

Demystifying the control plane: the easy upgrade path from GitOps with BigConfig

BigConfig Store

For many engineering teams, GitOps has been a game-changer, providing a declarative way to manage infrastructure and applications. But as complexity grows, you may find your processes hitting a ceiling. The natural next step? Upgrading to a control Plane.

Often, teams hesitate, believing this shift requires a costly, painful rewrite of their entire configuration management solution when it is written in Terraform or Ansible. They fear increased cognitive load and massive sunk costs.

This is where BigConfig changes the narrative. With BigConfig, you can upgrade your existing GitOps solution to a full-fledged control plane without rewriting everything from scratch or overwhelming your team.

Control planes in BigConfig

rama-jdbc

A control plane acts as an API for provisioning and managing infrastructure. Well-known examples include AWS itself and Kubernetes (K8s).

A common pain point when using infrastructure-as-code (IaC) tools like Terraform (using HCL) and GitOps is the difficulty in transitioning or upgrading to an internal control plane.

Teams that have invested significant time in writing Terraform’s HCL code traditionally face a complete rewrite to build a custom control plane API over their existing infrastructure definitions.

This limitation is no longer the case with BigConfig. We’ve demonstrated that a functional control plane can be created with as little as 200 lines of code, leveraging existing Terraform configurations.

Reimplementing the AWS EKS API with Clojure using BigConfig, Rama, and Pedestal

K8s

The world of cloud infrastructure often involves interacting with complex APIs. While services like AWS EKS provide robust management for Kubernetes clusters, there might be scenarios where you need a more tailored or localized control plane. This article will guide you through reimplementing the AWS EKS API using a powerful Clojure stack: Pedestal for the API, BigConfig to wrap Terraform and Ansible in a workflow, and Rama for state and jobs.