ObjectMeta for machine object

Spec contains the specification of the machine

Status contains fields depicting the status

NodeTemplate contains subfields to track all node resources and other node info required to scale nodegroup from zero

CredentialsSecretRef can optionally store the credentials (in this case the SecretRef does not need to store them). This might be useful if multiple machine classes with the same credentials but different user-datas are used.

Provider-specific configuration to use during node creation.

Provider is the combination of name and location of cloud-specific drivers.

SecretRef stores the necessary secrets such as credentials or userdata.

Standard object metadata.

Specification of the desired behavior of the MachineDeployment.

Most recently observed status of the MachineDeployment.

API group to which it belongs

Kind for machine class

Name of machine class

Last update time of current status

Description of the current operation

ErrorCode of the current operation if any

Last update time of current operation

State of operation

Type of operation

MachineDraintimeout is the timeout after which machine is forcefully deleted.

MachineHealthTimeout is the timeout after which machine is declared unhealhty/failed.

MachineCreationTimeout is the timeout after which machinie creation is declared failed.

MaxEvictRetries is the number of retries that will be attempted while draining the node.

NodeConditions are the set of conditions if set to true for MachineHealthTimeOut, machine will be declared failed.

Type of MachineDeployment condition.

Status of the condition, one of True, False, Unknown.

The last time this condition was updated.

Last time the condition transitioned from one status to another.

The reason for the condition’s last transition.

A human readable message indicating details about the transition.

Number of desired machines. This is a pointer to distinguish between explicit zero and not specified. Defaults to 0.

Label selector for machines. Existing MachineSets whose machines are selected by this will be the ones affected by this MachineDeployment.

Template describes the machines that will be created.

The MachineDeployment strategy to use to replace existing machines with new ones.

Minimum number of seconds for which a newly created machine should be ready without any of its container crashing, for it to be considered available. Defaults to 0 (machine will be considered available as soon as it is ready)

The number of old MachineSets to retain to allow rollback. This is a pointer to distinguish between explicit zero and not specified.

Indicates that the MachineDeployment is paused and will not be processed by the MachineDeployment controller.

DEPRECATED. The config this MachineDeployment is rolling back to. Will be cleared after rollback is done.

The maximum time in seconds for a MachineDeployment to make progress before it is considered to be failed. The MachineDeployment controller will continue to process failed MachineDeployments and a condition with a ProgressDeadlineExceeded reason will be surfaced in the MachineDeployment status. Note that progress will not be estimated during the time a MachineDeployment is paused. This is not set by default, which is treated as infinite deadline.

The generation observed by the MachineDeployment controller.

Total number of non-terminated machines targeted by this MachineDeployment (their labels match the selector).

Total number of non-terminated machines targeted by this MachineDeployment that have the desired template spec.

Total number of ready machines targeted by this MachineDeployment.

Total number of available machines (ready for at least minReadySeconds) targeted by this MachineDeployment.

Total number of unavailable machines targeted by this MachineDeployment. This is the total number of machines that are still required for the MachineDeployment to have 100% available capacity. They may either be machines that are running but not yet available or machines that still have not been created.

Represents the latest available observations of a MachineDeployment’s current state.

Count of hash collisions for the MachineDeployment. The MachineDeployment controller uses this field as a collision avoidance mechanism when it needs to create the name for the newest MachineSet.

FailedMachines has summary of machines on which lastOperation Failed

Type of MachineDeployment. Can be “Recreate” or “RollingUpdate”. Default is RollingUpdate.

Rolling update config params. Present only if MachineDeploymentStrategyType =

RollingUpdate.

TODO: Update this to follow our convention for oneOf, whatever we decide it to be.

Type of machine set condition.

Status of the condition, one of True, False, Unknown.

The last time the condition transitioned from one status to another.

The reason for the condition’s last transition.

A human readable message indicating details about the transition.

Replicas is the number of actual replicas.

The number of pods that have labels matching the labels of the pod template of the replicaset.

The number of ready replicas for this replica set.

The number of available replicas (ready for at least minReadySeconds) for this replica set.

ObservedGeneration is the most recent generation observed by the controller.

Represents the latest available observations of a replica set’s current state.

LastOperation performed

FailedMachines has summary of machines on which lastOperation Failed

Class contains the machineclass attributes of a machine

ProviderID represents the provider’s unique ID given to a machine

NodeTemplateSpec describes the data a node should have when created from a template

(Members of MachineConfiguration are embedded into this type.)

Configuration for the machine-controller.

Conditions of this machine, same as node

Last operation refers to the status of the last operation performed

Current status of the machine object

LastKnownState can store details of the last known state of the VM by the plugins. It can be used by future operation calls to determine current infrastucture state

Name of the machine object

ProviderID represents the provider’s unique ID given to a machine

Last operation refers to the status of the last operation performed

OwnerRef

Standard object’s metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata

Specification of the desired behavior of the machine. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#spec-and-status

Capacity contains subfields to track all node resources required to scale nodegroup from zero

Instance type of the node belonging to nodeGroup

Region of the expected node belonging to nodeGroup

Zone of the expected node belonging to nodeGroup

CPU Architecture of the node belonging to nodeGroup

NodeSpec describes the attributes that a node is created with.

The revision to rollback to. If set to 0, rollback to the last revision.

The maximum number of machines that can be unavailable during the update. Value can be an absolute number (ex: 5) or a percentage of desired machines (ex: 10%). Absolute number is calculated from percentage by rounding down. This can not be 0 if MaxSurge is 0. By default, a fixed value of 1 is used. Example: when this is set to 30%, the old MC can be scaled down to 70% of desired machines immediately when the rolling update starts. Once new machines are ready, old MC can be scaled down further, followed by scaling up the new MC, ensuring that the total number of machines available at all times during the update is at least 70% of desired machines.

The maximum number of machines that can be scheduled above the desired number of machines. Value can be an absolute number (ex: 5) or a percentage of desired machines (ex: 10%). This can not be 0 if MaxUnavailable is 0. Absolute number is calculated from percentage by rounding up. By default, a value of 1 is used. Example: when this is set to 30%, the new MC can be scaled up immediately when the rolling update starts, such that the total number of old and new machines do not exceed 130% of desired machines. Once old machines have been killed, new MC can be scaled up further, ensuring that total number of machines running at any time during the update is atmost 130% of desired machines.