Configuration
The Configuration section of kubriX explains how the Internal Developer Platform (IDP) is structured, configured, and customized to fit different environments and customer needs.
kubriX follows a modular configuration model built around Helm values files, allowing both turnkey installations and fine-grained customization.
This approach makes it possible to deliver a stable, secure, and well-integrated platform while keeping it flexible for diverse infrastructure setups.
Overview
Configuration Structure →
Learn how kubriX organizes and prioritizes its configuration files.
This document describes:
- The modular Helm-based values file system
- The reasoning behind multiple configuration layers
- The order of evaluation and override logic
- The role of installation variables such as
KUBRIX_CLUSTER_TYPEorKUBRIX_TSHIRT_SIZE
This overview is essential for understanding how kubriX assembles a full configuration stack.
Customizing kubriX for Your Needs →
Once you understand the base configuration structure, this guide explains how to adapt kubriX to your own use case:
- Adding or overriding Helm values safely
- Managing environment-specific or customer-specific settings
- Working with bootstrap-generated values
- Using
KUBRIX_APP_EXCLUDEand other installation variables for selective deployments
- Start from the defaults: Use the shipped
values-kubrix-default.yamlas your foundation. - Add modular overrides: Extend configuration through dedicated values files instead of editing defaults directly.
- Keep overrides visible: Maintain a clear separation between kubriX-provided and customer-specific configuration.
- Validate early: Use
helm lintand CI rendering previews to ensure configuration consistency before deployment. - Prefer maps over lists: This allows simpler overrides and better composability.