confighub-usage-guide

You can manage Kubernetes configuration drift by centralizing configurations as data using ConfigHub. It stores fully rendered configurations per environment, enabling centralized validation, drift correction, and safe change workflows across dev, staging, and prod spaces.

Configuration as data is an approach that stores fully rendered Kubernetes configurations per environment in a centralized hub. It enables policy-driven validation triggers, change management, and coordinated deployments across development, staging, and production spaces.

To set up ConfigHub, install and configure the cub CLI, then set your default space context. You create spaces for each environment, apply policy-driven validation triggers, and clone units across environments to coordinate deployments.

Yes, you can apply policy-driven validation triggers within your ConfigHub spaces. These triggers enforce configuration governance by validating change sets and coordinating deployments across multiple environments.

Yes, the cub CLI is required to manage configurations and orchestrate Kubernetes deployments with ConfigHub. You also need space context setup and policy-driven unit workflows to enforce configuration governance.

You can clone units across environments using the cub CLI within your configured spaces. This process manages change sets, links, and targets to coordinate safe deployments and maintain configuration governance across environments.