Merge pull request #364 from ingvagabund/set-min-length-for-mdb-crd

MDB: Set minimum value constraint for MinAvailable and MaxUnavailable

install/0000_30_machine-api-operator_08_machinedisruptionbudget.crd.yaml

@@ -53,13 +53,15 @@ spec:
                 one can prevent all voluntary deletions by specifying 0. This is a
                 mutually exclusive setting with "minAvailable".
               format: int32
+              minimum: 0
               type: integer
             minAvailable:
               description: An deletion of the machine is allowed if at least "minAvailable"
                 machines selected by "selector" will still be available after the
                 deletion. So for example you can prevent all voluntary deletions by
                 specifying all available nodes.
               format: int32
+              minimum: 0
               type: integer
             selector:
               description: Label query over machines whose deletions are managed by

pkg/apis/healthchecking/v1alpha1/machinedisruptionbudget_types.go

@@ -10,6 +10,7 @@ type MachineDisruptionBudgetSpec struct {
 	// "selector" will still be available after the deletion.
 	// So for example you can prevent all voluntary deletions by specifying all available nodes.
 	// +optional
+	// +kubebuilder:validation:Minimum=0
 	MinAvailable *int32 `json:"minAvailable,omitempty" protobuf:"bytes,1,opt,name=minAvailable"`
 
 	// Label query over machines whose deletions are managed by the disruption
@@ -22,6 +23,7 @@ type MachineDisruptionBudgetSpec struct {
 	// For example, one can prevent all voluntary deletions by specifying 0.
 	// This is a mutually exclusive setting with "minAvailable".
 	// +optional
+	// +kubebuilder:validation:Minimum=0
 	MaxUnavailable *int32 `json:"maxUnavailable,omitempty" protobuf:"bytes,3,opt,name=maxUnavailable"`
 }