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
// Status.Conditions was introduced in v1alpha4, thus requiring a custom conversion function; the values is going to be preserved in an annotation thus allowing roundtrip without loosing informations
162
+
funcConvert_v1alpha4_MachineDeploymentStatus_To_v1alpha3_MachineDeploymentStatus(in*v1alpha4.MachineDeploymentStatus, out*MachineDeploymentStatus, s apiconversion.Scope) error {
Copy file name to clipboardExpand all lines: api/v1alpha4/condition_consts.go
+11Lines changed: 11 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -201,3 +201,14 @@ const (
201
201
// from making any further remediations.
202
202
TooManyUnhealthyReason="TooManyUnhealthy"
203
203
)
204
+
205
+
// Conditions and condition Reasons for MachineDeployments
206
+
207
+
const (
208
+
// MachineDeploymentAvailableCondition means the MachineDeployment is available, that is, at least the minimum available
209
+
// machines required (i.e. Spec.Replicas-MaxUnavailable when MachineDeploymentStrategyType = RollingUpdate) are up and running for at least minReadySeconds.
// WaitingForAvailableMachinesReason (Severity=Warning) reflects the fact that the required minimum number of machines for a machinedeployment are not available.
// NOTE: The structure of calculateStatus() does not allow us to update the machinedeployment directly, we can only update the status obj it returns. Ideally, we should change calculateStatus() --> updateStatus() to be consistent with the rest of the code base, until then, we update conditions here.
0 commit comments