Machine [machine.openshift.io/v1beta1]

Description

Machine is the Schema for the machines API Compatibility level 2: Stable within a major release for a minimum of 9 months or 3 minor releases (whichever is longer).

Type

`object`

Specification

Property	Type	Description
`apiVersion`	`string`	APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources
`kind`	`string`	Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds
`metadata`	`ObjectMeta`	Standard object’s metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata
`spec`	`object`	MachineSpec defines the desired state of Machine
`status`	`object`	MachineStatus defines the observed state of Machine

.spec

Description

MachineSpec defines the desired state of Machine

Type

`object`

Property	Type	Description
`lifecycleHooks`	`object`	lifecycleHooks allow users to pause operations on the machine at certain predefined points within the machine lifecycle.
`metadata`	`object`	ObjectMeta will autopopulate the Node created. Use this to indicate what labels, annotations, name prefix, etc., should be used when creating the Node.
`providerID`	`string`	providerID is the identification ID of the machine provided by the provider. This field must match the provider ID as seen on the node object corresponding to this machine. This field is required by higher level consumers of cluster-api. Example use case is cluster autoscaler with cluster-api as provider. Clean-up logic in the autoscaler compares machines to nodes to find out machines at provider which could not get registered as Kubernetes nodes. With cluster-api as a generic out-of-tree provider for autoscaler, this field is required by autoscaler to be able to have a provider view of the list of machines. Another list of nodes is queried from the k8s apiserver and then a comparison is done to find out unregistered machines and are marked for delete. This field will be set by the actuators and consumed by higher level entities like autoscaler that will be interfacing with cluster-api as generic provider.
`providerSpec`	`object`	providerSpec details Provider-specific configuration to use during node creation.
`taints`	`array`	The list of the taints to be applied to the corresponding Node in additive manner. This list will not overwrite any other taints added to the Node on an ongoing basis by other entities. These taints should be actively reconciled e.g. if you ask the machine controller to apply a taint and then manually remove the taint the machine controller will put it back) but not have the machine controller remove any taints
`taints[]`	`object`	The node this Taint is attached to has the "effect" on any pod that does not tolerate the Taint.

.spec.lifecycleHooks

Description

lifecycleHooks allow users to pause operations on the machine at certain predefined points within the machine lifecycle.

Type

`object`

Property	Type	Description
`preDrain`	`array`	preDrain hooks prevent the machine from being drained. This also blocks further lifecycle events, such as termination.
`preDrain[]`	`object`	LifecycleHook represents a single instance of a lifecycle hook
`preTerminate`	`array`	preTerminate hooks prevent the machine from being terminated. PreTerminate hooks be actioned after the Machine has been drained.
`preTerminate[]`	`object`	LifecycleHook represents a single instance of a lifecycle hook

.spec.lifecycleHooks.preDrain

Description

preDrain hooks prevent the machine from being drained. This also blocks further lifecycle events, such as termination.

Type

`array`

.spec.lifecycleHooks.preDrain[]

Description

LifecycleHook represents a single instance of a lifecycle hook

Type

`object`

Required

name
owner

Property	Type	Description
`name`	`string`	name defines a unique name for the lifcycle hook. The name should be unique and descriptive, ideally 1-3 words, in CamelCase or it may be namespaced, eg. foo.example.com/CamelCase. Names must be unique and should only be managed by a single entity.
`owner`	`string`	owner defines the owner of the lifecycle hook. This should be descriptive enough so that users can identify who/what is responsible for blocking the lifecycle. This could be the name of a controller (e.g. clusteroperator/etcd) or an administrator managing the hook.

.spec.lifecycleHooks.preTerminate

Description

preTerminate hooks prevent the machine from being terminated. PreTerminate hooks be actioned after the Machine has been drained.

Type

`array`

.spec.lifecycleHooks.preTerminate[]

Description

LifecycleHook represents a single instance of a lifecycle hook

Type

`object`

Required

name
owner

Property	Type	Description
`name`	`string`	name defines a unique name for the lifcycle hook. The name should be unique and descriptive, ideally 1-3 words, in CamelCase or it may be namespaced, eg. foo.example.com/CamelCase. Names must be unique and should only be managed by a single entity.
`owner`	`string`	owner defines the owner of the lifecycle hook. This should be descriptive enough so that users can identify who/what is responsible for blocking the lifecycle. This could be the name of a controller (e.g. clusteroperator/etcd) or an administrator managing the hook.

.spec.metadata

Description

ObjectMeta will autopopulate the Node created. Use this to indicate what labels, annotations, name prefix, etc., should be used when creating the Node.

Type

`object`

Property	Type	Description
`annotations`	`object (string)`	annotations is an unstructured key value map stored with a resource that may be set by external tools to store and retrieve arbitrary metadata. They are not queryable and should be preserved when modifying objects. More info: http://kubernetes.io/docs/user-guide/annotations
`generateName`	`string`	generateName is an optional prefix, used by the server, to generate a unique name ONLY IF the Name field has not been provided. If this field is used, the name returned to the client will be different than the name passed. This value will also be combined with a unique suffix. The provided value has the same validation rules as the Name field, and may be truncated by the length of the suffix required to make the value unique on the server. If this field is specified and the generated name exists, the server will NOT return a 409 - instead, it will either return 201 Created or 500 with Reason ServerTimeout indicating a unique name could not be found in the time allotted, and the client should retry (optionally after the time indicated in the Retry-After header). Applied only if Name is not specified. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#idempotency
`labels`	`object (string)`	Map of string keys and values that can be used to organize and categorize (scope and select) objects. May match selectors of replication controllers and services. More info: http://kubernetes.io/docs/user-guide/labels
`name`	`string`	name must be unique within a namespace. Is required when creating resources, although some resources may allow a client to request the generation of an appropriate name automatically. Name is primarily intended for creation idempotence and configuration definition. Cannot be updated. More info: http://kubernetes.io/docs/user-guide/identifiers#names
`namespace`	`string`	namespace defines the space within each name must be unique. An empty namespace is equivalent to the "default" namespace, but "default" is the canonical representation. Not all objects are required to be scoped to a namespace - the value of this field for those objects will be empty. Must be a DNS_LABEL. Cannot be updated. More info: http://kubernetes.io/docs/user-guide/namespaces
`ownerReferences`	`array`	List of objects depended by this object. If ALL objects in the list have been deleted, this object will be garbage collected. If this object is managed by a controller, then an entry in this list will point to this controller, with the controller field set to true. There cannot be more than one managing controller.
`ownerReferences[]`	`object`	OwnerReference contains enough information to let you identify an owning object. An owning object must be in the same namespace as the dependent, or be cluster-scoped, so there is no namespace field.

.spec.metadata.ownerReferences

Description

List of objects depended by this object. If ALL objects in the list have been deleted, this object will be garbage collected. If this object is managed by a controller, then an entry in this list will point to this controller, with the controller field set to true. There cannot be more than one managing controller.

Type

`array`

.spec.metadata.ownerReferences[]

Description

OwnerReference contains enough information to let you identify an owning object. An owning object must be in the same namespace as the dependent, or be cluster-scoped, so there is no namespace field.

Type

`object`

Required

apiVersion
kind
name
uid

Property	Type	Description
`apiVersion`	`string`	API version of the referent.
`blockOwnerDeletion`	`boolean`	If true, AND if the owner has the "foregroundDeletion" finalizer, then the owner cannot be deleted from the key-value store until this reference is removed. See https://kubernetes.io/docs/concepts/architecture/garbage-collection/#foreground-deletion for how the garbage collector interacts with this field and enforces the foreground deletion. Defaults to false. To set this field, a user needs "delete" permission of the owner, otherwise 422 (Unprocessable Entity) will be returned.
`controller`	`boolean`	If true, this reference points to the managing controller.
`kind`	`string`	Kind of the referent. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds
`name`	`string`	Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names#names
`uid`	`string`	UID of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names#uids

.spec.providerSpec

Description

providerSpec details Provider-specific configuration to use during node creation.

Type

`object`

Property	Type	Description
`value`	``	value is an inlined, serialized representation of the resource configuration. It is recommended that providers maintain their own versioned API types that should be serialized/deserialized from this field, akin to component config.

.spec.taints

Description

The list of the taints to be applied to the corresponding Node in additive manner. This list will not overwrite any other taints added to the Node on an ongoing basis by other entities. These taints should be actively reconciled e.g. if you ask the machine controller to apply a taint and then manually remove the taint the machine controller will put it back) but not have the machine controller remove any taints

Type

`array`

.spec.taints[]

Description

The node this Taint is attached to has the "effect" on any pod that does not tolerate the Taint.

Type

`object`

Required

effect
key

Property	Type	Description
`effect`	`string`	Required. The effect of the taint on pods that do not tolerate the taint. Valid effects are NoSchedule, PreferNoSchedule and NoExecute.
`key`	`string`	Required. The taint key to be applied to a node.
`timeAdded`	`string`	TimeAdded represents the time at which the taint was added.
`value`	`string`	The taint value corresponding to the taint key.

.status

Description

MachineStatus defines the observed state of Machine

Type

`object`

Property	Type	Description
`addresses`	`array`	addresses is a list of addresses assigned to the machine. Queried from cloud provider, if available.
`addresses[]`	`object`	NodeAddress contains information for the node’s address.
`conditions`	`array`	conditions defines the current state of the Machine
`conditions[]`	`object`	Condition defines an observation of a Machine API resource operational state.
`errorMessage`	`string`	errorMessage will be set in the event that there is a terminal problem reconciling the Machine and will contain a more verbose string suitable for logging and human consumption. This field should not be set for transitive errors that a controller faces that are expected to be fixed automatically over time (like service outages), but instead indicate that something is fundamentally wrong with the Machine’s spec or the configuration of the controller, and that manual intervention is required. Examples of terminal errors would be invalid combinations of settings in the spec, values that are unsupported by the controller, or the responsible controller itself being critically misconfigured. Any transient errors that occur during the reconciliation of Machines can be added as events to the Machine object and/or logged in the controller’s output.
`errorReason`	`string`	errorReason will be set in the event that there is a terminal problem reconciling the Machine and will contain a succinct value suitable for machine interpretation. This field should not be set for transitive errors that a controller faces that are expected to be fixed automatically over time (like service outages), but instead indicate that something is fundamentally wrong with the Machine’s spec or the configuration of the controller, and that manual intervention is required. Examples of terminal errors would be invalid combinations of settings in the spec, values that are unsupported by the controller, or the responsible controller itself being critically misconfigured. Any transient errors that occur during the reconciliation of Machines can be added as events to the Machine object and/or logged in the controller’s output.
`lastOperation`	`object`	lastOperation describes the last-operation performed by the machine-controller. This API should be useful as a history in terms of the latest operation performed on the specific machine. It should also convey the state of the latest-operation for example if it is still on-going, failed or completed successfully.
`lastUpdated`	`string`	lastUpdated identifies when this status was last observed.
`nodeRef`	`object`	nodeRef will point to the corresponding Node if it exists.
`phase`	`string`	phase represents the current phase of machine actuation. One of: Failed, Provisioning, Provisioned, Running, Deleting
`providerStatus`	``	providerStatus details a Provider-specific status. It is recommended that providers maintain their own versioned API types that should be serialized/deserialized from this field.

.status.addresses

Description

addresses is a list of addresses assigned to the machine. Queried from cloud provider, if available.

Type

`array`

.status.addresses[]

Description

NodeAddress contains information for the node’s address.

Type

`object`

Required

address
type

Property	Type	Description
`address`	`string`	The node address.
`type`	`string`	Node address type, one of Hostname, ExternalIP or InternalIP.

.status.conditions

Description

conditions defines the current state of the Machine

Type

`array`

.status.conditions[]

Description

Condition defines an observation of a Machine API resource operational state.

Type

`object`

Required

lastTransitionTime
status
type

Property	Type	Description
`lastTransitionTime`	`string`	Last time the condition transitioned from one status to another. This should be when the underlying condition changed. If that is not known, then using the time when the API field changed is acceptable.
`message`	`string`	A human readable message indicating details about the transition. This field may be empty.
`reason`	`string`	The reason for the condition’s last transition in CamelCase. The specific API may choose whether or not this field is considered a guaranteed API. This field may not be empty.
`severity`	`string`	severity provides an explicit classification of Reason code, so the users or machines can immediately understand the current situation and act accordingly. The Severity field MUST be set only when Status=False.
`status`	`string`	status of the condition, one of True, False, Unknown.
`type`	`string`	type of condition in CamelCase or in foo.example.com/CamelCase. Many .condition.type values are consistent across resources like Available, but because arbitrary conditions can be useful (see .node.status.conditions), the ability to deconflict is important.

.status.lastOperation

Description

lastOperation describes the last-operation performed by the machine-controller. This API should be useful as a history in terms of the latest operation performed on the specific machine. It should also convey the state of the latest-operation for example if it is still on-going, failed or completed successfully.

Type

`object`

Property	Type	Description
`description`	`string`	description is the human-readable description of the last operation.
`lastUpdated`	`string`	lastUpdated is the timestamp at which LastOperation API was last-updated.
`state`	`string`	state is the current status of the last performed operation. E.g. Processing, Failed, Successful etc
`type`	`string`	type is the type of operation which was last performed. E.g. Create, Delete, Update etc

.status.nodeRef

Description

nodeRef will point to the corresponding Node if it exists.

Type

`object`

Property	Type	Description
`apiVersion`	`string`	API version of the referent.
`fieldPath`	`string`	If referring to a piece of an object instead of an entire object, this string should contain a valid JSON/Go field access statement, such as desiredState.manifest.containers[2]. For example, if the object reference is to a container within a pod, this would take on a value like: "spec.containers{name}" (where "name" refers to the name of the container that triggered the event) or if no container name is specified "spec.containers[2]" (container with index 2 in this pod). This syntax is chosen only to have some well-defined way of referencing a part of an object.
`kind`	`string`	Kind of the referent. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds
`name`	`string`	Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names
`namespace`	`string`	Namespace of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/
`resourceVersion`	`string`	Specific resourceVersion to which this reference is made, if any. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#concurrency-control-and-consistency
`uid`	`string`	UID of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#uids

API endpoints

The following API endpoints are available:

/apis/machine.openshift.io/v1beta1/machines
- GET: list objects of kind Machine
/apis/machine.openshift.io/v1beta1/namespaces/{namespace}/machines
- DELETE: delete collection of Machine
- GET: list objects of kind Machine
- POST: create a Machine
/apis/machine.openshift.io/v1beta1/namespaces/{namespace}/machines/{name}
- DELETE: delete a Machine
- GET: read the specified Machine
- PATCH: partially update the specified Machine
- PUT: replace the specified Machine
/apis/machine.openshift.io/v1beta1/namespaces/{namespace}/machines/{name}/status
- GET: read status of the specified Machine
- PATCH: partially update status of the specified Machine
- PUT: replace status of the specified Machine

/apis/machine.openshift.io/v1beta1/machines

HTTP method

`GET`

Description

list objects of kind Machine

HTTP responses

HTTP code	Reponse body
200 - OK	`MachineList` schema
401 - Unauthorized	Empty

/apis/machine.openshift.io/v1beta1/namespaces/{namespace}/machines

HTTP method

`DELETE`

Description

delete collection of Machine

HTTP responses

HTTP code	Reponse body
200 - OK	`Status` schema
401 - Unauthorized	Empty

HTTP method

`GET`

Description

list objects of kind Machine

HTTP responses

HTTP code	Reponse body
200 - OK	`MachineList` schema
401 - Unauthorized	Empty

HTTP method

`POST`

Description

create a Machine

Query parameters

Parameter	Type	Description
`dryRun`	`string`	When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed
`fieldValidation`	`string`	fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.

Body parameters

Parameter	Type	Description
`body`	`Machine` schema

HTTP responses

HTTP code	Reponse body
200 - OK	`Machine` schema
201 - Created	`Machine` schema
202 - Accepted	`Machine` schema
401 - Unauthorized	Empty

/apis/machine.openshift.io/v1beta1/namespaces/{namespace}/machines/{name}

Global path parameters

Parameter	Type	Description
`name`	`string`	name of the Machine

HTTP method

`DELETE`

Description

delete a Machine

Query parameters

Parameter	Type	Description
`dryRun`	`string`	When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed

HTTP responses

HTTP code	Reponse body
200 - OK	`Status` schema
202 - Accepted	`Status` schema
401 - Unauthorized	Empty

HTTP method

`GET`

Description

read the specified Machine

HTTP responses

HTTP code	Reponse body
200 - OK	`Machine` schema
401 - Unauthorized	Empty

HTTP method

`PATCH`

Description

partially update the specified Machine

Query parameters

Parameter	Type	Description
`dryRun`	`string`	When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed
`fieldValidation`	`string`	fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.

HTTP responses

HTTP code	Reponse body
200 - OK	`Machine` schema
401 - Unauthorized	Empty

HTTP method

`PUT`

Description

replace the specified Machine

Query parameters

Parameter	Type	Description
`dryRun`	`string`	When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed
`fieldValidation`	`string`	fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.

Body parameters

Parameter	Type	Description
`body`	`Machine` schema

HTTP responses

HTTP code	Reponse body
200 - OK	`Machine` schema
201 - Created	`Machine` schema
401 - Unauthorized	Empty

/apis/machine.openshift.io/v1beta1/namespaces/{namespace}/machines/{name}/status

Global path parameters

Parameter	Type	Description
`name`	`string`	name of the Machine

HTTP method

`GET`

Description

read status of the specified Machine

HTTP responses

HTTP code	Reponse body
200 - OK	`Machine` schema
401 - Unauthorized	Empty

HTTP method

`PATCH`

Description

partially update status of the specified Machine

Query parameters

Parameter	Type	Description
`dryRun`	`string`	When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed
`fieldValidation`	`string`	fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.

HTTP responses

HTTP code	Reponse body
200 - OK	`Machine` schema
401 - Unauthorized	Empty

HTTP method

`PUT`

Description

replace status of the specified Machine

Query parameters

Parameter	Type	Description
`dryRun`	`string`	When present, indicates that modifications should not be persisted. An invalid or unrecognized dryRun directive will result in an error response and no further processing of the request. Valid values are: - All: all dry run stages will be processed
`fieldValidation`	`string`	fieldValidation instructs the server on how to handle objects in the request (POST/PUT/PATCH) containing unknown or duplicate fields. Valid values are: - Ignore: This will ignore any unknown fields that are silently dropped from the object, and will ignore all but the last duplicate field that the decoder encounters. This is the default behavior prior to v1.23. - Warn: This will send a warning via the standard warning response header for each unknown field that is dropped from the object, and for each duplicate field that is encountered. The request will still succeed if there are no other errors, and will only persist the last of any duplicate fields. This is the default in v1.23+ - Strict: This will fail the request with a BadRequest error if any unknown fields would be dropped from the object, or if any duplicate fields are present. The error returned from the server will contain all unknown and duplicate fields encountered.

Body parameters

Parameter	Type	Description
`body`	`Machine` schema

HTTP responses

HTTP code	Reponse body
200 - OK	`Machine` schema
201 - Created	`Machine` schema
401 - Unauthorized	Empty

Machine [machine.openshift.io/v1beta1]¶

Specification¶

.spec¶

.spec.lifecycleHooks¶

.spec.lifecycleHooks.preDrain¶

.spec.lifecycleHooks.preDrain[]¶

.spec.lifecycleHooks.preTerminate¶

.spec.lifecycleHooks.preTerminate[]¶

.spec.metadata¶

.spec.metadata.ownerReferences¶

.spec.metadata.ownerReferences[]¶

.spec.providerSpec¶

.spec.taints¶

.spec.taints[]¶

.status¶

.status.addresses¶

.status.addresses[]¶

.status.conditions¶

.status.conditions[]¶

.status.lastOperation¶

.status.nodeRef¶

API endpoints¶

/apis/machine.openshift.io/v1beta1/machines¶

/apis/machine.openshift.io/v1beta1/namespaces/{namespace}/machines¶

/apis/machine.openshift.io/v1beta1/namespaces/{namespace}/machines/{name}¶

/apis/machine.openshift.io/v1beta1/namespaces/{namespace}/machines/{name}/status¶

Machine [machine.openshift.io/v1beta1]

Specification

.spec

.spec.lifecycleHooks

.spec.lifecycleHooks.preDrain

.spec.lifecycleHooks.preDrain[]

.spec.lifecycleHooks.preTerminate

.spec.lifecycleHooks.preTerminate[]

.spec.metadata

.spec.metadata.ownerReferences

.spec.metadata.ownerReferences[]

.spec.providerSpec

.spec.taints

.spec.taints[]

.status

.status.addresses

.status.addresses[]

.status.conditions

.status.conditions[]

.status.lastOperation

.status.nodeRef

API endpoints

/apis/machine.openshift.io/v1beta1/machines

/apis/machine.openshift.io/v1beta1/namespaces/{namespace}/machines

/apis/machine.openshift.io/v1beta1/namespaces/{namespace}/machines/{name}

/apis/machine.openshift.io/v1beta1/namespaces/{namespace}/machines/{name}/status