CRD Management

Learn how Bluebricks automatically handles Custom Resource Definitions (CRDs) in your Helm charts using FluxCD Server-Side Apply for reliable, consistent deployments.

Overview

Bluebricks uses FluxCD Server-Side Apply (SSA) to manage CRD installation automatically. This ensures CRDs are installed before your chart deploys, preventing common deployment failures and version conflicts.

CRD Support

Automatic Installation:

• CRDs are automatically installed before chart deployment

• Uses FluxCD SSA for reliable CRD management

• Handles CRD updates and versioning

CRD Sources:

• crds/ directory in your chart

• Chart dependencies with CRDs

• External CRD definitions

CRD Directory Structure

my-helm-chart/
├── Chart.yaml
├── values.yaml
├── templates/
└── crds/                    # CRD definitions
    ├── custom-resource.yaml
    └── another-crd.yaml

How CRD Installation Works

Bluebricks follows a safe, sequential process to handle CRDs:

1. Pre-deployment: Installs CRDs first to make them available

2. Validation: Validates CRD syntax and compatibility before proceeding

3. Chart deployment: Deploys your chart templates that reference the CRDs

4. Post-deployment: Verifies CRD status to confirm successful installation

This order prevents errors where templates try to use CRDs that don't exist yet.

Best Practices

1. Place CRDs in crds/ directory

2. Use proper CRD versions

3. Test CRD installation locally

4. Document CRD requirements

See also

• How to Create a Helm Artifact -- package your Helm chart for Bluebricks

• Packages overview -- artifact types and packaging concepts