Removing default value of FailedNodeStartupTimeout

Signed-off-by: Michael Shitrit <mshitrit@redhat.com>
openshift · Jun 29, 2021 · e3d7784 · e3d7784
1 parent f1e9ae5
commit e3d7784
Show file tree

Hide file tree

Showing 2 changed files with 0 additions and 2 deletions.
diff --git a/install/0000_30_machine-api-operator_07_machinehealthcheck.crd.yaml b/install/0000_30_machine-api-operator_07_machinehealthcheck.crd.yaml
@@ -56,7 +56,6 @@ spec:
             description: Specification of machine health check policy
             properties:
               failedNodeStartupTimeout:
-                default: 48h
                 description: Failed Machines that are older than this value and are
                   without a nodeRef or a providerID will be considered to have passed
                   the time period allocated for a manual fix and will be remediated.

diff --git a/pkg/apis/machine/v1beta1/machinehealthcheck_types.go b/pkg/apis/machine/v1beta1/machinehealthcheck_types.go
@@ -89,7 +89,6 @@ type MachineHealthCheckSpec struct {
 	// fraction and a unit suffix, eg "300ms", "1.5h" or "2h45m".
 	// Valid time units are "ns", "us" (or "µs"), "ms", "s", "m", "h".
 	// +optional
-	// +kubebuilder:default:="48h"
 	// +kubebuilder:validation:Pattern="^([0-9]+(\\.[0-9]+)?(ns|us|µs|ms|s|m|h))+$"
 	// +kubebuilder:validation:Type:=string
 	FailedNodeStartupTimeout metav1.Duration `json:"failedNodeStartupTimeout,omitempty"`