Declarative Configuration

The core control mechanism that makes declarative configuration work. A reconciliation loop continuously observes the current state of a resource, compares it against the declared desired state, and automatically executes corrective actions to eliminate any drift. This pattern is the engine behind Kubernetes controllers and GitOps operators, ensuring the network always converges to the user's intent without requiring a human to script the specific steps.

A higher-level abstraction that applies declarative logic to entire business policies. Instead of declaring the state of a single resource, an administrator states a business intent like 'Ensure gold-tier VoIP traffic has less than 10ms of jitter.' The IBN system translates this intent into concrete declarative configurations, continuously validates the outcome, and takes corrective action if the business objective is not met, closing the loop between business language and device state.

An operational framework that uses a Git repository as the single source of truth for declarative infrastructure. All desired state configurations are stored as code. A software agent like Argo CD or Flux monitors the repo and automatically reconciles the live environment to match it. This provides a complete audit trail for every change, enables simple rollbacks via git revert, and enforces strict separation of duties where no one needs direct access to production infrastructure.

The practice of managing and provisioning infrastructure through machine-readable definition files rather than interactive tools or physical hardware configuration. Tools like Terraform and Pulumi use a declarative model where you define the final topology, and the engine calculates the dependency graph and execution plan to reach that state. This eliminates configuration drift, enables version control for infrastructure, and makes the entire provisioning process repeatable and auditable.

A critical mathematical property for declarative automation. An idempotent operation produces the exact same result no matter how many times it is executed. In provisioning, this means a configuration script can be safely re-run without creating duplicate resources, partial states, or errors. Declarative engines rely on idempotency to safely execute reconciliation loops, as the controller can repeatedly attempt to apply the desired state without fear of side effects.

The automated process of detecting and correcting unauthorized changes to a system's configuration. Drift occurs when a manual hotfix, an automated process, or a security breach modifies a live resource away from its declared desired state. A declarative system with drift remediation will automatically detect this deviation and re-apply the desired configuration, restoring compliance and ensuring the network's actual state continuously converges back to the single source of truth.