You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
operator: add PodDisruptionBudget support to Pipeline CRD
Add spec.budget field to Pipeline with maxUnavailable/minAvailable
options, following the convention used by Strimzi and Prometheus
Operator. The PDB is rendered by the Syncer alongside the Deployment
and ConfigMap, so it is automatically garbage-collected on CR deletion.
CRD validation enforces exactly one of maxUnavailable or minAvailable
via CEL rule. RBAC updated for policy/poddisruptionbudgets.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
// PipelineBudget configures a PodDisruptionBudget for the pipeline.
194
+
// Exactly one of MaxUnavailable or MinAvailable must be specified.
195
+
// +kubebuilder:validation:XValidation:message="exactly one of maxUnavailable or minAvailable must be set",rule="has(self.maxUnavailable) != has(self.minAvailable)"
196
+
typePipelineBudgetstruct {
197
+
// MaxUnavailable is the maximum number of pipeline pods that can be
198
+
// unavailable during a voluntary disruption. Can be an absolute number
0 commit comments