Documentation
¶
Overview ¶
reconciler/pipeline_reconciler.go
A custom reconciler for the Pipeline CRD. This implements domain.Reconciler directly — the GenericReconciler is not used at all.
Use a constructor when:
- The reconcile loop itself must be controlled (state machine, phased execution)
- You are migrating an existing controller-runtime reconciler
- The GenericReconciler's hook model is not sufficient
Orkestra still provides — even with a custom constructor:
- Informer watching the Pipeline CRD
- Workqueue with deduplication and backoff
- Worker pool (configurable workers per Katalog)
- safeReconcile panic recovery
- Prometheus metrics (reconcile total, duration, queue depth)
- Per-CRD health tracking
The constructor owns — and is responsible for:
- Reading objects from the informer cache
- Finalizer management
- Kubernetes events
- Status updates
- All reconcile and delete logic
Index ¶
Constants ¶
This section is empty.
Variables ¶
This section is empty.
Functions ¶
func NewPipelineReconciler ¶
func NewPipelineReconciler( kube *kubeclient.Kubeclient, informer cache.SharedIndexInformer, ev *event.Event, ) domain.Reconciler
NewPipelineReconciler is the constructor function registered in the Katalog. Signature matches what Orkestra expects: (kube, informer, ev) → domain.Reconciler.
Types ¶
type PipelineReconciler ¶
type PipelineReconciler struct {
// contains filtered or unexported fields
}
PipelineReconciler implements domain.Reconciler for the Pipeline CRD. It drives the Pipeline through its lifecycle phases:
Pending → Running → Succeeded | Failed
Source Files
Click to show internal directories.
Click to hide internal directories.