Configuration lifecycle

Clearplane separates saving configuration from making it active at Edge. This keeps related changes coherent and makes pending work visible.

From source to Edge

1. An operator saves a UI or REST API change, or container discovery observes a label change.
2. Core validates and persists the accepted change. A material change advances the configuration revision.
3. When that revision is applied, Edge fetches the complete enabled routes, clusters, destinations, and policy assignments.
4. Edge validates the complete candidate and publishes it as one routing snapshot.

Edge never activates a partial candidate. If loading fails, the previous valid snapshot continues serving requests and the new revision remains pending.

Apply modes

• Immediate takes effect after its save or reconciliation succeeds.
• Validated takes effect only after Clearplane accepts the complete value.
• Apply required is staged until automatic apply runs or an operator chooses Apply on the relevant service.
• Restart required remains pending until the affected service restarts through an approved operating workflow.

The exact mode belongs to each setting. Check its row in Reference rather than assuming that every setting from the same source behaves alike.

Revisions and pending state

Edge reports the revision it has loaded, allowing the UI to distinguish applying work from changes still waiting to be applied.

Container-discovered route changes use the same revision path.

Follow Change and apply configuration for the operator workflow.