README
¶
Component Prerequisites
This example demonstrates how to use component-level prerequisites with DependsOn to order components within a
controller.
What it shows
- Two components, one controller: The "infra" component manages a ConfigMap and reports
InfraReady. The "app" component manages a Deployment and reportsAppReady. - DependsOn prerequisite: The app component uses
WithPrerequisite(component.DependsOn("InfraReady"))to block until the infra component's condition isTrue. - Permanent pass: Once a prerequisite is satisfied, it is never re-evaluated. Subsequent reconciles proceed without checking it again.
- Sequential reconciliation: The controller reconciles infra first, then app. The owner's in-memory status is
updated between the two calls, so
DependsOncan read the first component's condition.
Reconciliation steps
- Full reconciliation: infra sets
InfraReady=True, then app's prerequisite passes and it proceeds. - Version upgrade: both components reconcile normally (prerequisite already passed).
Running
go run ./examples/component-prerequisites/.
Documentation
¶
Overview ¶
Package main demonstrates component-level prerequisites with DependsOn.
Two components share one owner. The "infra" component manages a ConfigMap and reports InfraReady. The "app" component manages a Deployment and uses DependsOn("InfraReady") to wait for the infra component before proceeding.
Source Files
Directories
¶
| Path | Synopsis |
|---|---|
|
Package app provides a sample controller demonstrating component-level prerequisites.
|
Package app provides a sample controller demonstrating component-level prerequisites. |
|
Package resources provides resource factories for the component-prerequisites example.
|
Package resources provides resource factories for the component-prerequisites example. |
Click to show internal directories.
Click to hide internal directories.