Helm

Overview

Helm packages enable you to manage Kubernetes applications using standard Helm charts while leveraging Bluebricks’ orchestration and deployment automation. With a Helm artifact, you can package, configure, and deploy services to any Kubernetes cluster using declarative chart definitions, ensuring consistent and repeatable releases across environments.

By turning your Helm chart into a reusable artifact, Bluebricks allows you to centralize configuration, apply environment-specific values, and streamline release operations. Each deployment is fully tracked, versioned, and auditable, giving teams clear visibility into chart changes, rendered manifests, and applied resources. Moreover, Helm charts can be executed in one workflow with other IaC, for a streamlined provisioning process, without manually initiating each section separately.

Bluebricks also enhances the Helm workflow with built-in capabilities that simplify Kubernetes-based deployments, including:

• Flexible values management, enabling overrides from inputs, secrets, or dynamically generated data

• Consistent release management across environments, with clear tracking of release history and rendered diffs

• Integration with Kubernetes credentials and cluster contexts, reducing manual configuration and setup

• Automated handling of chart dependencies and templating, ensuring reliable packaging and execution

Package Dependencies and Data Flow

Packages expose inputs (properties) and outputs, enabling them to participate in flexible, modular dependency chains orchestrated through a directed acyclic graph (DAG).

Inputs define the parameters a package requires and can be statically defined or dynamically derived using expressions that reference other packages, blueprint properties, or secrets. These expressions create explicit dependencies between packages, allowing the orchestrator to determine the correct execution order. Inputs also support conditional expressions, enabling packages to be included or excluded based on runtime context.

Outputs represent values produced during package execution—such as resource identifiers, endpoints, or computed configurations—and become available for consumption by downstream packages. This creates a bidirectional dependency flow where packages can safely reference one another’s results.

This design enables unified orchestration across multiple infrastructure-as-code technologies—Terraform, Helm, Bicep, and CloudFormation can coexist within a single blueprint, sharing data and dependencies seamlessly. The orchestrator provides a single plan, single execution flow, and unified state management regardless of the underlying IaC tool. Packages can be sourced from artifacts or directly from Git repositories, allowing complex systems to be built from small, reusable, independently versionable units. The dependency graph is calculated at plan time, ensuring deterministic execution order and enabling parallel execution where dependencies allow.