config-center

What problem does it solve?

ConfigCenter turns scattered configuration sources into a consistent, reliable controller pipeline so route and dependency changes propagate correctly without requiring manual reloads or backend-specific logic.

Core Features & Use Cases

• Unified ConfCenter abstraction: Provides a single interface for CRUD operations and lifecycle management across backends.
• Same Workqueue + ResourceProcessor pipeline: Ensures deterministic dedup, validation, parsing, dependency resolution, and status writeback regardless of event source.
• Multi-backend implementations: Supports FileSystemCenter for dev/test, KubernetesCenter for production HA with leader election, and an etcd-backed design constraint for single-writer deployments.
• Cross-resource dependency requeue: Tracks bidirectional references (e.g., Secret/Service/ReferenceGrant) and requeues dependents safely using trigger-chain cycle bounds.
• Status handling and persistence strategy: Writes K8s status via status subresource in Kubernetes mode and persists YAML .status files in file-system mode.

Quick Start

Generate or update an HTTPRoute YAML in the configured source (local directory or Kubernetes), and let ConfigCenter validate, parse references, update caches, and reconcile dependent resources automatically.