Provisioning APIs
Reference guide for provisioning APIs
Abstract
Chapter 1. Provisioning APIs
1.1. BMCEventSubscription [metal3.io/v1alpha1]
- Description
- BMCEventSubscription is the Schema for the fast eventing API
- Type
-
object
1.2. BareMetalHost [metal3.io/v1alpha1]
- Description
- BareMetalHost is the Schema for the baremetalhosts API
- Type
-
object
1.3. DataImage [metal3.io/v1alpha1]
- Description
- DataImage is the Schema for the dataimages API.
- Type
-
object
1.4. FirmwareSchema [metal3.io/v1alpha1]
- Description
- FirmwareSchema is the Schema for the firmwareschemas API.
- Type
-
object
1.5. HardwareData [metal3.io/v1alpha1]
- Description
- HardwareData is the Schema for the hardwaredata API.
- Type
-
object
1.6. HostFirmwareComponents [metal3.io/v1alpha1]
- Description
- HostFirmwareComponents is the Schema for the hostfirmwarecomponents API.
- Type
-
object
1.7. HostFirmwareSettings [metal3.io/v1alpha1]
- Description
- HostFirmwareSettings is the Schema for the hostfirmwaresettings API.
- Type
-
object
1.8. Metal3Remediation [infrastructure.cluster.x-k8s.io/v1beta1]
- Description
- Metal3Remediation is the Schema for the metal3remediations API.
- Type
-
object
1.9. Metal3RemediationTemplate [infrastructure.cluster.x-k8s.io/v1beta1]
- Description
- Metal3RemediationTemplate is the Schema for the metal3remediationtemplates API.
- Type
-
object
1.10. PreprovisioningImage [metal3.io/v1alpha1]
- Description
- PreprovisioningImage is the Schema for the preprovisioningimages API.
- Type
-
object
1.11. Provisioning [metal3.io/v1alpha1]
- Description
- Provisioning contains configuration used by the Provisioning service (Ironic) to provision baremetal hosts. Provisioning is created by the OpenShift installer using admin or user provided information about the provisioning network and the NIC on the server that can be used to PXE boot it. This CR is a singleton, created by the installer and currently only consumed by the cluster-baremetal-operator to bring up and update containers in a metal3 cluster.
- Type
-
object
Chapter 2. BMCEventSubscription [metal3.io/v1alpha1]
- Description
- BMCEventSubscription is the Schema for the fast eventing API
- Type
-
object
2.1. Specification
Property | Type | Description |
---|---|---|
|
| 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 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 |
| Standard object’s metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata | |
|
| |
|
|
2.1.1. .spec
- Description
- Type
-
object
Property | Type | Description |
---|---|---|
|
| Arbitrary user-provided context for the event |
|
| A webhook URL to send events to |
|
| A reference to a BareMetalHost |
|
| A secret containing HTTP headers which should be passed along to the Destination when making a request |
2.1.2. .spec.httpHeadersRef
- Description
- A secret containing HTTP headers which should be passed along to the Destination when making a request
- Type
-
object
Property | Type | Description |
---|---|---|
|
| name is unique within a namespace to reference a secret resource. |
|
| namespace defines the space within which the secret name must be unique. |
2.1.3. .status
- Description
- Type
-
object
Property | Type | Description |
---|---|---|
|
| |
|
|
2.2. API endpoints
The following API endpoints are available:
/apis/metal3.io/v1alpha1/bmceventsubscriptions
-
GET
: list objects of kind BMCEventSubscription
-
/apis/metal3.io/v1alpha1/namespaces/{namespace}/bmceventsubscriptions
-
DELETE
: delete collection of BMCEventSubscription -
GET
: list objects of kind BMCEventSubscription -
POST
: create a BMCEventSubscription
-
/apis/metal3.io/v1alpha1/namespaces/{namespace}/bmceventsubscriptions/{name}
-
DELETE
: delete a BMCEventSubscription -
GET
: read the specified BMCEventSubscription -
PATCH
: partially update the specified BMCEventSubscription -
PUT
: replace the specified BMCEventSubscription
-
/apis/metal3.io/v1alpha1/namespaces/{namespace}/bmceventsubscriptions/{name}/status
-
GET
: read status of the specified BMCEventSubscription -
PATCH
: partially update status of the specified BMCEventSubscription -
PUT
: replace status of the specified BMCEventSubscription
-
2.2.1. /apis/metal3.io/v1alpha1/bmceventsubscriptions
- HTTP method
-
GET
- Description
- list objects of kind BMCEventSubscription
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
2.2.2. /apis/metal3.io/v1alpha1/namespaces/{namespace}/bmceventsubscriptions
- HTTP method
-
DELETE
- Description
- delete collection of BMCEventSubscription
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
- HTTP method
-
GET
- Description
- list objects of kind BMCEventSubscription
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
- HTTP method
-
POST
- Description
- create a BMCEventSubscription
Parameter | Type | Description |
---|---|---|
|
| 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 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. |
Parameter | Type | Description |
---|---|---|
|
|
HTTP code | Reponse body |
---|---|
200 - OK |
|
201 - Created |
|
202 - Accepted |
|
401 - Unauthorized | Empty |
2.2.3. /apis/metal3.io/v1alpha1/namespaces/{namespace}/bmceventsubscriptions/{name}
Parameter | Type | Description |
---|---|---|
|
| name of the BMCEventSubscription |
- HTTP method
-
DELETE
- Description
- delete a BMCEventSubscription
Parameter | Type | Description |
---|---|---|
|
| 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 code | Reponse body |
---|---|
200 - OK |
|
202 - Accepted |
|
401 - Unauthorized | Empty |
- HTTP method
-
GET
- Description
- read the specified BMCEventSubscription
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
- HTTP method
-
PATCH
- Description
- partially update the specified BMCEventSubscription
Parameter | Type | Description |
---|---|---|
|
| 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 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 code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
- HTTP method
-
PUT
- Description
- replace the specified BMCEventSubscription
Parameter | Type | Description |
---|---|---|
|
| 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 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. |
Parameter | Type | Description |
---|---|---|
|
|
HTTP code | Reponse body |
---|---|
200 - OK |
|
201 - Created |
|
401 - Unauthorized | Empty |
2.2.4. /apis/metal3.io/v1alpha1/namespaces/{namespace}/bmceventsubscriptions/{name}/status
Parameter | Type | Description |
---|---|---|
|
| name of the BMCEventSubscription |
- HTTP method
-
GET
- Description
- read status of the specified BMCEventSubscription
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
- HTTP method
-
PATCH
- Description
- partially update status of the specified BMCEventSubscription
Parameter | Type | Description |
---|---|---|
|
| 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 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 code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
- HTTP method
-
PUT
- Description
- replace status of the specified BMCEventSubscription
Parameter | Type | Description |
---|---|---|
|
| 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 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. |
Parameter | Type | Description |
---|---|---|
|
|
HTTP code | Reponse body |
---|---|
200 - OK |
|
201 - Created |
|
401 - Unauthorized | Empty |
Chapter 3. BareMetalHost [metal3.io/v1alpha1]
- Description
- BareMetalHost is the Schema for the baremetalhosts API
- Type
-
object
3.1. Specification
Property | Type | Description |
---|---|---|
|
| 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 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 |
| Standard object’s metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata | |
|
| BareMetalHostSpec defines the desired state of BareMetalHost. |
|
| BareMetalHostStatus defines the observed state of BareMetalHost. |
3.1.1. .spec
- Description
- BareMetalHostSpec defines the desired state of BareMetalHost.
- Type
-
object
- Required
-
online
-
Property | Type | Description |
---|---|---|
|
| CPU architecture of the host, e.g. "x86_64" or "aarch64". If unset, eventually populated by inspection. |
|
| When set to disabled, automated cleaning will be avoided during provisioning and deprovisioning. |
|
| How do we connect to the BMC? |
|
| Which MAC address will PXE boot? This is optional for some types, but required for libvirt VMs driven by vbmc. |
|
| Select the method of initializing the hardware during boot. Defaults to UEFI. |
|
| ConsumerRef can be used to store information about something that is using a host. When it is not empty, the host is considered "in use". |
|
| A custom deploy procedure. |
|
| Description is a human-entered text used to help identify the host |
|
| ExternallyProvisioned means something else is managing the image running on the host and the operator should only manage the power status and hardware inventory inspection. If the Image field is filled in, this field is ignored. |
|
| BIOS configuration for bare metal server |
|
| What is the name of the hardware profile for this host? Hardware profiles are deprecated and should not be used. Use the separate fields Architecture and RootDeviceHints instead. Set to "empty" to prepare for the future version of the API without hardware profiles. |
|
| Image holds the details of the image to be provisioned. |
|
| MetaData holds the reference to the Secret containing host metadata (e.g. meta_data.json) which is passed to the Config Drive. |
|
| NetworkData holds the reference to the Secret containing network configuration (e.g content of network_data.json) which is passed to the Config Drive. |
|
| Should the server be online? |
|
| PreprovisioningNetworkDataName is the name of the Secret in the local namespace containing network configuration (e.g content of network_data.json) which is passed to the preprovisioning image, and to the Config Drive if not overridden by specifying NetworkData. |
|
| RAID configuration for bare metal server |
|
| Provide guidance about how to choose the device for the image being provisioned. |
|
| Taints is the full, authoritative list of taints to apply to the corresponding Machine. This list will overwrite any modifications made to the Machine on an ongoing basis. |
|
| The node this Taint is attached to has the "effect" on any pod that does not tolerate the Taint. |
|
| UserData holds the reference to the Secret containing the user data to be passed to the host before it boots. |
3.1.2. .spec.bmc
- Description
- How do we connect to the BMC?
- Type
-
object
- Required
-
address
-
credentialsName
-
Property | Type | Description |
---|---|---|
|
| Address holds the URL for accessing the controller on the network. |
|
| The name of the secret containing the BMC credentials (requires keys "username" and "password"). |
|
| DisableCertificateVerification disables verification of server certificates when using HTTPS to connect to the BMC. This is required when the server certificate is self-signed, but is insecure because it allows a man-in-the-middle to intercept the connection. |
3.1.3. .spec.consumerRef
- Description
- ConsumerRef can be used to store information about something that is using a host. When it is not empty, the host is considered "in use".
- Type
-
object
Property | Type | Description |
---|---|---|
|
| API version of the referent. |
|
| 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. TODO: this design is not final and this field is subject to change in the future. |
|
| Kind of the referent. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds |
|
| Name of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names |
|
| Namespace of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/ |
|
| 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 of the referent. More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#uids |
3.1.4. .spec.customDeploy
- Description
- A custom deploy procedure.
- Type
-
object
- Required
-
method
-
Property | Type | Description |
---|---|---|
|
| Custom deploy method name. This name is specific to the deploy ramdisk used. If you don’t have a custom deploy ramdisk, you shouldn’t use CustomDeploy. |
3.1.5. .spec.firmware
- Description
- BIOS configuration for bare metal server
- Type
-
object
Property | Type | Description |
---|---|---|
|
| Allows a single physical processor core to appear as several logical processors. This supports following options: true, false. |
|
| SR-IOV support enables a hypervisor to create virtual instances of a PCI-express device, potentially increasing performance. This supports following options: true, false. |
|
| Supports the virtualization of platform hardware. This supports following options: true, false. |
3.1.6. .spec.image
- Description
- Image holds the details of the image to be provisioned.
- Type
-
object
- Required
-
url
-
Property | Type | Description |
---|---|---|
|
| Checksum is the checksum for the image. |
|
| ChecksumType is the checksum algorithm for the image, e.g md5, sha256 or sha512. The special value "auto" can be used to detect the algorithm from the checksum. If missing, MD5 is used. If in doubt, use "auto". |
|
| DiskFormat contains the format of the image (raw, qcow2, …). Needs to be set to raw for raw images streaming. Note live-iso means an iso referenced by the url will be live-booted and not deployed to disk, and in this case the checksum options are not required and if specified will be ignored. |
|
| URL is a location of an image to deploy. |
3.1.7. .spec.metaData
- Description
- MetaData holds the reference to the Secret containing host metadata (e.g. meta_data.json) which is passed to the Config Drive.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| name is unique within a namespace to reference a secret resource. |
|
| namespace defines the space within which the secret name must be unique. |
3.1.8. .spec.networkData
- Description
- NetworkData holds the reference to the Secret containing network configuration (e.g content of network_data.json) which is passed to the Config Drive.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| name is unique within a namespace to reference a secret resource. |
|
| namespace defines the space within which the secret name must be unique. |
3.1.9. .spec.raid
- Description
- RAID configuration for bare metal server
- Type
-
object
Property | Type | Description |
---|---|---|
| `` |
The list of logical disks for hardware RAID, if rootDeviceHints isn’t used, first volume is root volume. You can set the value of this field to |
| `` | The list of logical disks for software RAID, if rootDeviceHints isn’t used, first volume is root volume. If HardwareRAIDVolumes is set this item will be invalid. The number of created Software RAID devices must be 1 or 2. If there is only one Software RAID device, it has to be a RAID-1. If there are two, the first one has to be a RAID-1, while the RAID level for the second one can be 0, 1, or 1+0. As the first RAID device will be the deployment device, enforcing a RAID-1 reduces the risk of ending up with a non-booting node in case of a disk failure. Software RAID will always be deleted. |
3.1.10. .spec.rootDeviceHints
- Description
- Provide guidance about how to choose the device for the image being provisioned.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| A Linux device name like "/dev/vda", or a by-path link to it like "/dev/disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0". The hint must match the actual value exactly. |
|
| A SCSI bus address like 0:0:0:0. The hint must match the actual value exactly. |
|
| The minimum size of the device in Gigabytes. |
|
| A vendor-specific device identifier. The hint can be a substring of the actual value. |
|
| True if the device should use spinning media, false otherwise. |
|
| Device serial number. The hint must match the actual value exactly. |
|
| The name of the vendor or manufacturer of the device. The hint can be a substring of the actual value. |
|
| Unique storage identifier. The hint must match the actual value exactly. |
|
| Unique vendor storage identifier. The hint must match the actual value exactly. |
|
| Unique storage identifier with the vendor extension appended. The hint must match the actual value exactly. |
3.1.11. .spec.taints
- Description
- Taints is the full, authoritative list of taints to apply to the corresponding Machine. This list will overwrite any modifications made to the Machine on an ongoing basis.
- Type
-
array
3.1.12. .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 |
---|---|---|
|
| Required. The effect of the taint on pods that do not tolerate the taint. Valid effects are NoSchedule, PreferNoSchedule and NoExecute. |
|
| Required. The taint key to be applied to a node. |
|
| TimeAdded represents the time at which the taint was added. It is only written for NoExecute taints. |
|
| The taint value corresponding to the taint key. |
3.1.13. .spec.userData
- Description
- UserData holds the reference to the Secret containing the user data to be passed to the host before it boots.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| name is unique within a namespace to reference a secret resource. |
|
| namespace defines the space within which the secret name must be unique. |
3.1.14. .status
- Description
- BareMetalHostStatus defines the observed state of BareMetalHost.
- Type
-
object
- Required
-
errorCount
-
errorMessage
-
hardwareProfile
-
operationalStatus
-
poweredOn
-
provisioning
-
Property | Type | Description |
---|---|---|
|
| ErrorCount records how many times the host has encoutered an error since the last successful operation |
|
| the last error message reported by the provisioning subsystem |
|
| ErrorType indicates the type of failure encountered when the OperationalStatus is OperationalStatusError |
|
| the last credentials we were able to validate as working |
|
| The hardware discovered to exist on the host. |
|
| The name of the profile matching the hardware details. |
|
| LastUpdated identifies when this status was last observed. |
|
| OperationHistory holds information about operations performed on this host. |
|
| OperationalStatus holds the status of the host |
|
| indicator for whether or not the host is powered on |
|
| Information tracked by the provisioner. |
|
| the last credentials we sent to the provisioning backend |
3.1.15. .status.goodCredentials
- Description
- the last credentials we were able to validate as working
- Type
-
object
Property | Type | Description |
---|---|---|
|
| SecretReference represents a Secret Reference. It has enough information to retrieve secret in any namespace |
|
|
3.1.16. .status.goodCredentials.credentials
- Description
- SecretReference represents a Secret Reference. It has enough information to retrieve secret in any namespace
- Type
-
object
Property | Type | Description |
---|---|---|
|
| name is unique within a namespace to reference a secret resource. |
|
| namespace defines the space within which the secret name must be unique. |
3.1.17. .status.hardware
- Description
- The hardware discovered to exist on the host.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| CPU describes one processor on the host. |
|
| Firmware describes the firmware on the host. |
|
| |
|
| |
|
| NIC describes one network interface on the host. |
|
| |
|
| |
|
| Storage describes one storage device (disk, SSD, etc.) on the host. |
|
| HardwareSystemVendor stores details about the whole hardware system. |
3.1.18. .status.hardware.cpu
- Description
- CPU describes one processor on the host.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| |
|
| ClockSpeed is a clock speed in MHz |
|
| |
|
| |
|
|
3.1.19. .status.hardware.firmware
- Description
- Firmware describes the firmware on the host.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| The BIOS for this firmware |
3.1.20. .status.hardware.firmware.bios
- Description
- The BIOS for this firmware
- Type
-
object
Property | Type | Description |
---|---|---|
|
| The release/build date for this BIOS |
|
| The vendor name for this BIOS |
|
| The version of the BIOS |
3.1.21. .status.hardware.nics
- Description
- Type
-
array
3.1.22. .status.hardware.nics[]
- Description
- NIC describes one network interface on the host.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| The IP address of the interface. This will be an IPv4 or IPv6 address if one is present. If both IPv4 and IPv6 addresses are present in a dual-stack environment, two nics will be output, one with each IP. |
|
| The device MAC address |
|
| The vendor and product IDs of the NIC, e.g. "0x8086 0x1572" |
|
| The name of the network interface, e.g. "en0" |
|
| Whether the NIC is PXE Bootable |
|
| The speed of the device in Gigabits per second |
|
| The untagged VLAN ID |
|
| The VLANs available |
|
| VLAN represents the name and ID of a VLAN. |
3.1.23. .status.hardware.nics[].vlans
- Description
- The VLANs available
- Type
-
array
3.1.24. .status.hardware.nics[].vlans[]
- Description
- VLAN represents the name and ID of a VLAN.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| VLANID is a 12-bit 802.1Q VLAN identifier |
|
|
3.1.25. .status.hardware.storage
- Description
- Type
-
array
3.1.26. .status.hardware.storage[]
- Description
- Storage describes one storage device (disk, SSD, etc.) on the host.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| A list of alternate Linux device names of the disk, e.g. "/dev/sda". Note that this list is not exhaustive, and names may not be stable across reboots. |
|
| The SCSI location of the device |
|
| Hardware model |
|
| A Linux device name of the disk, e.g. "/dev/disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0". This will be a name that is stable across reboots if one is available. |
|
| Whether this disk represents rotational storage. This field is not recommended for usage, please prefer using 'Type' field instead, this field will be deprecated eventually. |
|
| The serial number of the device |
|
| The size of the disk in Bytes |
|
| Device type, one of: HDD, SSD, NVME. |
|
| The name of the vendor of the device |
|
| The WWN of the device |
|
| The WWN Vendor extension of the device |
|
| The WWN with the extension |
3.1.27. .status.hardware.systemVendor
- Description
- HardwareSystemVendor stores details about the whole hardware system.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| |
|
| |
|
|
3.1.28. .status.operationHistory
- Description
- OperationHistory holds information about operations performed on this host.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| OperationMetric contains metadata about an operation (inspection, provisioning, etc.) used for tracking metrics. |
|
| OperationMetric contains metadata about an operation (inspection, provisioning, etc.) used for tracking metrics. |
|
| OperationMetric contains metadata about an operation (inspection, provisioning, etc.) used for tracking metrics. |
|
| OperationMetric contains metadata about an operation (inspection, provisioning, etc.) used for tracking metrics. |
3.1.29. .status.operationHistory.deprovision
- Description
- OperationMetric contains metadata about an operation (inspection, provisioning, etc.) used for tracking metrics.
- Type
-
object
Property | Type | Description |
---|---|---|
| `` | |
| `` |
3.1.30. .status.operationHistory.inspect
- Description
- OperationMetric contains metadata about an operation (inspection, provisioning, etc.) used for tracking metrics.
- Type
-
object
Property | Type | Description |
---|---|---|
| `` | |
| `` |
3.1.31. .status.operationHistory.provision
- Description
- OperationMetric contains metadata about an operation (inspection, provisioning, etc.) used for tracking metrics.
- Type
-
object
Property | Type | Description |
---|---|---|
| `` | |
| `` |
3.1.32. .status.operationHistory.register
- Description
- OperationMetric contains metadata about an operation (inspection, provisioning, etc.) used for tracking metrics.
- Type
-
object
Property | Type | Description |
---|---|---|
| `` | |
| `` |
3.1.33. .status.provisioning
- Description
- Information tracked by the provisioner.
- Type
-
object
- Required
-
ID
-
state
-
Property | Type | Description |
---|---|---|
|
| The machine’s UUID from the underlying provisioning tool |
|
| BootMode indicates the boot mode used to provision the node |
|
| Custom deploy procedure applied to the host. |
|
| The Bios set by the user |
|
| Image holds the details of the last image successfully provisioned to the host. |
|
| The Raid set by the user |
|
| The RootDevicehints set by the user |
|
| An indiciator for what the provisioner is doing with the host. |
3.1.34. .status.provisioning.customDeploy
- Description
- Custom deploy procedure applied to the host.
- Type
-
object
- Required
-
method
-
Property | Type | Description |
---|---|---|
|
| Custom deploy method name. This name is specific to the deploy ramdisk used. If you don’t have a custom deploy ramdisk, you shouldn’t use CustomDeploy. |
3.1.35. .status.provisioning.firmware
- Description
- The Bios set by the user
- Type
-
object
Property | Type | Description |
---|---|---|
|
| Allows a single physical processor core to appear as several logical processors. This supports following options: true, false. |
|
| SR-IOV support enables a hypervisor to create virtual instances of a PCI-express device, potentially increasing performance. This supports following options: true, false. |
|
| Supports the virtualization of platform hardware. This supports following options: true, false. |
3.1.36. .status.provisioning.image
- Description
- Image holds the details of the last image successfully provisioned to the host.
- Type
-
object
- Required
-
url
-
Property | Type | Description |
---|---|---|
|
| Checksum is the checksum for the image. |
|
| ChecksumType is the checksum algorithm for the image, e.g md5, sha256 or sha512. The special value "auto" can be used to detect the algorithm from the checksum. If missing, MD5 is used. If in doubt, use "auto". |
|
| DiskFormat contains the format of the image (raw, qcow2, …). Needs to be set to raw for raw images streaming. Note live-iso means an iso referenced by the url will be live-booted and not deployed to disk, and in this case the checksum options are not required and if specified will be ignored. |
|
| URL is a location of an image to deploy. |
3.1.37. .status.provisioning.raid
- Description
- The Raid set by the user
- Type
-
object
Property | Type | Description |
---|---|---|
| `` |
The list of logical disks for hardware RAID, if rootDeviceHints isn’t used, first volume is root volume. You can set the value of this field to |
| `` | The list of logical disks for software RAID, if rootDeviceHints isn’t used, first volume is root volume. If HardwareRAIDVolumes is set this item will be invalid. The number of created Software RAID devices must be 1 or 2. If there is only one Software RAID device, it has to be a RAID-1. If there are two, the first one has to be a RAID-1, while the RAID level for the second one can be 0, 1, or 1+0. As the first RAID device will be the deployment device, enforcing a RAID-1 reduces the risk of ending up with a non-booting node in case of a disk failure. Software RAID will always be deleted. |
3.1.38. .status.provisioning.rootDeviceHints
- Description
- The RootDevicehints set by the user
- Type
-
object
Property | Type | Description |
---|---|---|
|
| A Linux device name like "/dev/vda", or a by-path link to it like "/dev/disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0". The hint must match the actual value exactly. |
|
| A SCSI bus address like 0:0:0:0. The hint must match the actual value exactly. |
|
| The minimum size of the device in Gigabytes. |
|
| A vendor-specific device identifier. The hint can be a substring of the actual value. |
|
| True if the device should use spinning media, false otherwise. |
|
| Device serial number. The hint must match the actual value exactly. |
|
| The name of the vendor or manufacturer of the device. The hint can be a substring of the actual value. |
|
| Unique storage identifier. The hint must match the actual value exactly. |
|
| Unique vendor storage identifier. The hint must match the actual value exactly. |
|
| Unique storage identifier with the vendor extension appended. The hint must match the actual value exactly. |
3.1.39. .status.triedCredentials
- Description
- the last credentials we sent to the provisioning backend
- Type
-
object
Property | Type | Description |
---|---|---|
|
| SecretReference represents a Secret Reference. It has enough information to retrieve secret in any namespace |
|
|
3.1.40. .status.triedCredentials.credentials
- Description
- SecretReference represents a Secret Reference. It has enough information to retrieve secret in any namespace
- Type
-
object
Property | Type | Description |
---|---|---|
|
| name is unique within a namespace to reference a secret resource. |
|
| namespace defines the space within which the secret name must be unique. |
3.2. API endpoints
The following API endpoints are available:
/apis/metal3.io/v1alpha1/baremetalhosts
-
GET
: list objects of kind BareMetalHost
-
/apis/metal3.io/v1alpha1/namespaces/{namespace}/baremetalhosts
-
DELETE
: delete collection of BareMetalHost -
GET
: list objects of kind BareMetalHost -
POST
: create a BareMetalHost
-
/apis/metal3.io/v1alpha1/namespaces/{namespace}/baremetalhosts/{name}
-
DELETE
: delete a BareMetalHost -
GET
: read the specified BareMetalHost -
PATCH
: partially update the specified BareMetalHost -
PUT
: replace the specified BareMetalHost
-
/apis/metal3.io/v1alpha1/namespaces/{namespace}/baremetalhosts/{name}/status
-
GET
: read status of the specified BareMetalHost -
PATCH
: partially update status of the specified BareMetalHost -
PUT
: replace status of the specified BareMetalHost
-
3.2.1. /apis/metal3.io/v1alpha1/baremetalhosts
- HTTP method
-
GET
- Description
- list objects of kind BareMetalHost
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
3.2.2. /apis/metal3.io/v1alpha1/namespaces/{namespace}/baremetalhosts
- HTTP method
-
DELETE
- Description
- delete collection of BareMetalHost
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
- HTTP method
-
GET
- Description
- list objects of kind BareMetalHost
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
- HTTP method
-
POST
- Description
- create a BareMetalHost
Parameter | Type | Description |
---|---|---|
|
| 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 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. |
Parameter | Type | Description |
---|---|---|
|
|
HTTP code | Reponse body |
---|---|
200 - OK |
|
201 - Created |
|
202 - Accepted |
|
401 - Unauthorized | Empty |
3.2.3. /apis/metal3.io/v1alpha1/namespaces/{namespace}/baremetalhosts/{name}
Parameter | Type | Description |
---|---|---|
|
| name of the BareMetalHost |
- HTTP method
-
DELETE
- Description
- delete a BareMetalHost
Parameter | Type | Description |
---|---|---|
|
| 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 code | Reponse body |
---|---|
200 - OK |
|
202 - Accepted |
|
401 - Unauthorized | Empty |
- HTTP method
-
GET
- Description
- read the specified BareMetalHost
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
- HTTP method
-
PATCH
- Description
- partially update the specified BareMetalHost
Parameter | Type | Description |
---|---|---|
|
| 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 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 code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
- HTTP method
-
PUT
- Description
- replace the specified BareMetalHost
Parameter | Type | Description |
---|---|---|
|
| 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 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. |
Parameter | Type | Description |
---|---|---|
|
|
HTTP code | Reponse body |
---|---|
200 - OK |
|
201 - Created |
|
401 - Unauthorized | Empty |
3.2.4. /apis/metal3.io/v1alpha1/namespaces/{namespace}/baremetalhosts/{name}/status
Parameter | Type | Description |
---|---|---|
|
| name of the BareMetalHost |
- HTTP method
-
GET
- Description
- read status of the specified BareMetalHost
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
- HTTP method
-
PATCH
- Description
- partially update status of the specified BareMetalHost
Parameter | Type | Description |
---|---|---|
|
| 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 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 code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
- HTTP method
-
PUT
- Description
- replace status of the specified BareMetalHost
Parameter | Type | Description |
---|---|---|
|
| 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 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. |
Parameter | Type | Description |
---|---|---|
|
|
HTTP code | Reponse body |
---|---|
200 - OK |
|
201 - Created |
|
401 - Unauthorized | Empty |
Chapter 4. DataImage [metal3.io/v1alpha1]
- Description
- DataImage is the Schema for the dataimages API.
- Type
-
object
4.1. Specification
Property | Type | Description |
---|---|---|
|
| 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 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 |
| Standard object’s metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata | |
|
| DataImageSpec defines the desired state of DataImage. |
|
| DataImageStatus defines the observed state of DataImage. |
4.1.1. .spec
- Description
- DataImageSpec defines the desired state of DataImage.
- Type
-
object
- Required
-
url
-
Property | Type | Description |
---|---|---|
|
| Url is the address of the dataImage that we want to attach to a BareMetalHost |
4.1.2. .status
- Description
- DataImageStatus defines the observed state of DataImage.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| Currently attached DataImage |
|
| Error count and message when attaching/detaching |
|
| Time of last reconciliation |
4.1.3. .status.attachedImage
- Description
- Currently attached DataImage
- Type
-
object
- Required
-
url
-
Property | Type | Description |
---|---|---|
|
|
4.1.4. .status.error
- Description
- Error count and message when attaching/detaching
- Type
-
object
- Required
-
count
-
message
-
Property | Type | Description |
---|---|---|
|
| |
|
|
4.2. API endpoints
The following API endpoints are available:
/apis/metal3.io/v1alpha1/dataimages
-
GET
: list objects of kind DataImage
-
/apis/metal3.io/v1alpha1/namespaces/{namespace}/dataimages
-
DELETE
: delete collection of DataImage -
GET
: list objects of kind DataImage -
POST
: create a DataImage
-
/apis/metal3.io/v1alpha1/namespaces/{namespace}/dataimages/{name}
-
DELETE
: delete a DataImage -
GET
: read the specified DataImage -
PATCH
: partially update the specified DataImage -
PUT
: replace the specified DataImage
-
/apis/metal3.io/v1alpha1/namespaces/{namespace}/dataimages/{name}/status
-
GET
: read status of the specified DataImage -
PATCH
: partially update status of the specified DataImage -
PUT
: replace status of the specified DataImage
-
4.2.1. /apis/metal3.io/v1alpha1/dataimages
- HTTP method
-
GET
- Description
- list objects of kind DataImage
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
4.2.2. /apis/metal3.io/v1alpha1/namespaces/{namespace}/dataimages
- HTTP method
-
DELETE
- Description
- delete collection of DataImage
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
- HTTP method
-
GET
- Description
- list objects of kind DataImage
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
- HTTP method
-
POST
- Description
- create a DataImage
Parameter | Type | Description |
---|---|---|
|
| 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 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. |
Parameter | Type | Description |
---|---|---|
|
|
HTTP code | Reponse body |
---|---|
200 - OK |
|
201 - Created |
|
202 - Accepted |
|
401 - Unauthorized | Empty |
4.2.3. /apis/metal3.io/v1alpha1/namespaces/{namespace}/dataimages/{name}
Parameter | Type | Description |
---|---|---|
|
| name of the DataImage |
- HTTP method
-
DELETE
- Description
- delete a DataImage
Parameter | Type | Description |
---|---|---|
|
| 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 code | Reponse body |
---|---|
200 - OK |
|
202 - Accepted |
|
401 - Unauthorized | Empty |
- HTTP method
-
GET
- Description
- read the specified DataImage
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
- HTTP method
-
PATCH
- Description
- partially update the specified DataImage
Parameter | Type | Description |
---|---|---|
|
| 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 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 code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
- HTTP method
-
PUT
- Description
- replace the specified DataImage
Parameter | Type | Description |
---|---|---|
|
| 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 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. |
Parameter | Type | Description |
---|---|---|
|
|
HTTP code | Reponse body |
---|---|
200 - OK |
|
201 - Created |
|
401 - Unauthorized | Empty |
4.2.4. /apis/metal3.io/v1alpha1/namespaces/{namespace}/dataimages/{name}/status
Parameter | Type | Description |
---|---|---|
|
| name of the DataImage |
- HTTP method
-
GET
- Description
- read status of the specified DataImage
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
- HTTP method
-
PATCH
- Description
- partially update status of the specified DataImage
Parameter | Type | Description |
---|---|---|
|
| 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 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 code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
- HTTP method
-
PUT
- Description
- replace status of the specified DataImage
Parameter | Type | Description |
---|---|---|
|
| 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 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. |
Parameter | Type | Description |
---|---|---|
|
|
HTTP code | Reponse body |
---|---|
200 - OK |
|
201 - Created |
|
401 - Unauthorized | Empty |
Chapter 5. FirmwareSchema [metal3.io/v1alpha1]
- Description
- FirmwareSchema is the Schema for the firmwareschemas API.
- Type
-
object
5.1. Specification
Property | Type | Description |
---|---|---|
|
| 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 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 |
| Standard object’s metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata | |
|
| FirmwareSchemaSpec defines the desired state of FirmwareSchema. |
5.1.1. .spec
- Description
- FirmwareSchemaSpec defines the desired state of FirmwareSchema.
- Type
-
object
- Required
-
schema
-
Property | Type | Description |
---|---|---|
|
| The hardware model associated with this schema |
|
| The hardware vendor associated with this schema |
|
| Map of firmware name to schema |
|
| Additional data describing the firmware setting. |
5.1.2. .spec.schema
- Description
- Map of firmware name to schema
- Type
-
object
5.1.3. .spec.schema{}
- Description
- Additional data describing the firmware setting.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| The allowable value for an Enumeration type setting. |
|
| The type of setting. |
|
| The lowest value for an Integer type setting. |
|
| Maximum length for a String type setting. |
|
| Minimum length for a String type setting. |
|
| Whether or not this setting is read only. |
|
| Whether or not this setting’s value is unique to this node, e.g. a serial number. |
|
| The highest value for an Integer type setting. |
5.2. API endpoints
The following API endpoints are available:
/apis/metal3.io/v1alpha1/firmwareschemas
-
GET
: list objects of kind FirmwareSchema
-
/apis/metal3.io/v1alpha1/namespaces/{namespace}/firmwareschemas
-
DELETE
: delete collection of FirmwareSchema -
GET
: list objects of kind FirmwareSchema -
POST
: create a FirmwareSchema
-
/apis/metal3.io/v1alpha1/namespaces/{namespace}/firmwareschemas/{name}
-
DELETE
: delete a FirmwareSchema -
GET
: read the specified FirmwareSchema -
PATCH
: partially update the specified FirmwareSchema -
PUT
: replace the specified FirmwareSchema
-
5.2.1. /apis/metal3.io/v1alpha1/firmwareschemas
- HTTP method
-
GET
- Description
- list objects of kind FirmwareSchema
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
5.2.2. /apis/metal3.io/v1alpha1/namespaces/{namespace}/firmwareschemas
- HTTP method
-
DELETE
- Description
- delete collection of FirmwareSchema
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
- HTTP method
-
GET
- Description
- list objects of kind FirmwareSchema
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
- HTTP method
-
POST
- Description
- create a FirmwareSchema
Parameter | Type | Description |
---|---|---|
|
| 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 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. |
Parameter | Type | Description |
---|---|---|
|
|
HTTP code | Reponse body |
---|---|
200 - OK |
|
201 - Created |
|
202 - Accepted |
|
401 - Unauthorized | Empty |
5.2.3. /apis/metal3.io/v1alpha1/namespaces/{namespace}/firmwareschemas/{name}
Parameter | Type | Description |
---|---|---|
|
| name of the FirmwareSchema |
- HTTP method
-
DELETE
- Description
- delete a FirmwareSchema
Parameter | Type | Description |
---|---|---|
|
| 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 code | Reponse body |
---|---|
200 - OK |
|
202 - Accepted |
|
401 - Unauthorized | Empty |
- HTTP method
-
GET
- Description
- read the specified FirmwareSchema
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
- HTTP method
-
PATCH
- Description
- partially update the specified FirmwareSchema
Parameter | Type | Description |
---|---|---|
|
| 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 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 code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
- HTTP method
-
PUT
- Description
- replace the specified FirmwareSchema
Parameter | Type | Description |
---|---|---|
|
| 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 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. |
Parameter | Type | Description |
---|---|---|
|
|
HTTP code | Reponse body |
---|---|
200 - OK |
|
201 - Created |
|
401 - Unauthorized | Empty |
Chapter 6. HardwareData [metal3.io/v1alpha1]
- Description
- HardwareData is the Schema for the hardwaredata API.
- Type
-
object
6.1. Specification
Property | Type | Description |
---|---|---|
|
| 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 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 |
| Standard object’s metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata | |
|
| HardwareDataSpec defines the desired state of HardwareData. |
6.1.1. .spec
- Description
- HardwareDataSpec defines the desired state of HardwareData.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| The hardware discovered on the host during its inspection. |
6.1.2. .spec.hardware
- Description
- The hardware discovered on the host during its inspection.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| CPU describes one processor on the host. |
|
| Firmware describes the firmware on the host. |
|
| |
|
| |
|
| NIC describes one network interface on the host. |
|
| |
|
| |
|
| Storage describes one storage device (disk, SSD, etc.) on the host. |
|
| HardwareSystemVendor stores details about the whole hardware system. |
6.1.3. .spec.hardware.cpu
- Description
- CPU describes one processor on the host.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| |
|
| ClockSpeed is a clock speed in MHz |
|
| |
|
| |
|
|
6.1.4. .spec.hardware.firmware
- Description
- Firmware describes the firmware on the host.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| The BIOS for this firmware |
6.1.5. .spec.hardware.firmware.bios
- Description
- The BIOS for this firmware
- Type
-
object
Property | Type | Description |
---|---|---|
|
| The release/build date for this BIOS |
|
| The vendor name for this BIOS |
|
| The version of the BIOS |
6.1.6. .spec.hardware.nics
- Description
- Type
-
array
6.1.7. .spec.hardware.nics[]
- Description
- NIC describes one network interface on the host.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| The IP address of the interface. This will be an IPv4 or IPv6 address if one is present. If both IPv4 and IPv6 addresses are present in a dual-stack environment, two nics will be output, one with each IP. |
|
| The device MAC address |
|
| The vendor and product IDs of the NIC, e.g. "0x8086 0x1572" |
|
| The name of the network interface, e.g. "en0" |
|
| Whether the NIC is PXE Bootable |
|
| The speed of the device in Gigabits per second |
|
| The untagged VLAN ID |
|
| The VLANs available |
|
| VLAN represents the name and ID of a VLAN. |
6.1.8. .spec.hardware.nics[].vlans
- Description
- The VLANs available
- Type
-
array
6.1.9. .spec.hardware.nics[].vlans[]
- Description
- VLAN represents the name and ID of a VLAN.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| VLANID is a 12-bit 802.1Q VLAN identifier |
|
|
6.1.10. .spec.hardware.storage
- Description
- Type
-
array
6.1.11. .spec.hardware.storage[]
- Description
- Storage describes one storage device (disk, SSD, etc.) on the host.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| A list of alternate Linux device names of the disk, e.g. "/dev/sda". Note that this list is not exhaustive, and names may not be stable across reboots. |
|
| The SCSI location of the device |
|
| Hardware model |
|
| A Linux device name of the disk, e.g. "/dev/disk/by-path/pci-0000:01:00.0-scsi-0:2:0:0". This will be a name that is stable across reboots if one is available. |
|
| Whether this disk represents rotational storage. This field is not recommended for usage, please prefer using 'Type' field instead, this field will be deprecated eventually. |
|
| The serial number of the device |
|
| The size of the disk in Bytes |
|
| Device type, one of: HDD, SSD, NVME. |
|
| The name of the vendor of the device |
|
| The WWN of the device |
|
| The WWN Vendor extension of the device |
|
| The WWN with the extension |
6.1.12. .spec.hardware.systemVendor
- Description
- HardwareSystemVendor stores details about the whole hardware system.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| |
|
| |
|
|
6.2. API endpoints
The following API endpoints are available:
/apis/metal3.io/v1alpha1/hardwaredata
-
GET
: list objects of kind HardwareData
-
/apis/metal3.io/v1alpha1/namespaces/{namespace}/hardwaredata
-
DELETE
: delete collection of HardwareData -
GET
: list objects of kind HardwareData -
POST
: create a HardwareData
-
/apis/metal3.io/v1alpha1/namespaces/{namespace}/hardwaredata/{name}
-
DELETE
: delete a HardwareData -
GET
: read the specified HardwareData -
PATCH
: partially update the specified HardwareData -
PUT
: replace the specified HardwareData
-
6.2.1. /apis/metal3.io/v1alpha1/hardwaredata
- HTTP method
-
GET
- Description
- list objects of kind HardwareData
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
6.2.2. /apis/metal3.io/v1alpha1/namespaces/{namespace}/hardwaredata
- HTTP method
-
DELETE
- Description
- delete collection of HardwareData
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
- HTTP method
-
GET
- Description
- list objects of kind HardwareData
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
- HTTP method
-
POST
- Description
- create a HardwareData
Parameter | Type | Description |
---|---|---|
|
| 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 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. |
Parameter | Type | Description |
---|---|---|
|
|
HTTP code | Reponse body |
---|---|
200 - OK |
|
201 - Created |
|
202 - Accepted |
|
401 - Unauthorized | Empty |
6.2.3. /apis/metal3.io/v1alpha1/namespaces/{namespace}/hardwaredata/{name}
Parameter | Type | Description |
---|---|---|
|
| name of the HardwareData |
- HTTP method
-
DELETE
- Description
- delete a HardwareData
Parameter | Type | Description |
---|---|---|
|
| 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 code | Reponse body |
---|---|
200 - OK |
|
202 - Accepted |
|
401 - Unauthorized | Empty |
- HTTP method
-
GET
- Description
- read the specified HardwareData
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
- HTTP method
-
PATCH
- Description
- partially update the specified HardwareData
Parameter | Type | Description |
---|---|---|
|
| 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 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 code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
- HTTP method
-
PUT
- Description
- replace the specified HardwareData
Parameter | Type | Description |
---|---|---|
|
| 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 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. |
Parameter | Type | Description |
---|---|---|
|
|
HTTP code | Reponse body |
---|---|
200 - OK |
|
201 - Created |
|
401 - Unauthorized | Empty |
Chapter 7. HostFirmwareComponents [metal3.io/v1alpha1]
- Description
- HostFirmwareComponents is the Schema for the hostfirmwarecomponents API.
- Type
-
object
7.1. Specification
Property | Type | Description |
---|---|---|
|
| 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 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 |
| Standard object’s metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata | |
|
| HostFirmwareComponentsSpec defines the desired state of HostFirmwareComponents. |
|
| HostFirmwareComponentsStatus defines the observed state of HostFirmwareComponents. |
7.1.1. .spec
- Description
- HostFirmwareComponentsSpec defines the desired state of HostFirmwareComponents.
- Type
-
object
- Required
-
updates
-
Property | Type | Description |
---|---|---|
|
| |
|
| FirmwareUpdate defines a firmware update specification. |
7.1.2. .spec.updates
- Description
- Type
-
array
7.1.3. .spec.updates[]
- Description
- FirmwareUpdate defines a firmware update specification.
- Type
-
object
- Required
-
component
-
url
-
Property | Type | Description |
---|---|---|
|
| |
|
|
7.1.4. .status
- Description
- HostFirmwareComponentsStatus defines the observed state of HostFirmwareComponents.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| Components is the list of all available firmware components and their information. |
|
| FirmwareComponentStatus defines the status of a firmware component. |
|
| Track whether updates stored in the spec are valid based on the schema |
|
|
Condition contains details for one aspect of the current state of this API Resource. --- This struct is intended for direct use as an array at the field path .status.conditions. For example, type FooStatus struct{ // Represents the observations of a foo’s current state. // Known .status.conditions.type are: "Available", "Progressing", and "Degraded" // +patchMergeKey=type // +patchStrategy=merge // +listType=map // +listMapKey=type Conditions []metav1.Condition |
|
| Time that the status was last updated |
|
| Updates is the list of all firmware components that should be updated they are specified via name and url fields. |
|
| FirmwareUpdate defines a firmware update specification. |
7.1.5. .status.components
- Description
- Components is the list of all available firmware components and their information.
- Type
-
array
7.1.6. .status.components[]
- Description
- FirmwareComponentStatus defines the status of a firmware component.
- Type
-
object
- Required
-
component
-
initialVersion
-
Property | Type | Description |
---|---|---|
|
| |
|
| |
|
| |
|
| |
|
|
7.1.7. .status.conditions
- Description
- Track whether updates stored in the spec are valid based on the schema
- Type
-
array
7.1.8. .status.conditions[]
- Description
-
Condition contains details for one aspect of the current state of this API Resource. --- This struct is intended for direct use as an array at the field path .status.conditions. For example, type FooStatus struct{ // Represents the observations of a foo’s current state. // Known .status.conditions.type are: "Available", "Progressing", and "Degraded" // +patchMergeKey=type // +patchStrategy=merge // +listType=map // +listMapKey=type Conditions []metav1.Condition
json:"conditions,omitempty" patchStrategy:"merge" patchMergeKey:"type" protobuf:"bytes,1,rep,name=conditions"
// other fields } - Type
-
object
- Required
-
lastTransitionTime
-
message
-
reason
-
status
-
type
-
Property | Type | Description |
---|---|---|
|
| lastTransitionTime is the 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 is a human readable message indicating details about the transition. This may be an empty string. |
|
| observedGeneration represents the .metadata.generation that the condition was set based upon. For instance, if .metadata.generation is currently 12, but the .status.conditions[x].observedGeneration is 9, the condition is out of date with respect to the current state of the instance. |
|
| reason contains a programmatic identifier indicating the reason for the condition’s last transition. Producers of specific condition types may define expected values and meanings for this field, and whether the values are considered a guaranteed API. The value should be a CamelCase string. This field may not be empty. |
|
| status of the condition, one of True, False, Unknown. |
|
| 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. The regex it matches is (dns1123SubdomainFmt/)?(qualifiedNameFmt) |
7.1.9. .status.updates
- Description
- Updates is the list of all firmware components that should be updated they are specified via name and url fields.
- Type
-
array
7.1.10. .status.updates[]
- Description
- FirmwareUpdate defines a firmware update specification.
- Type
-
object
- Required
-
component
-
url
-
Property | Type | Description |
---|---|---|
|
| |
|
|
7.2. API endpoints
The following API endpoints are available:
/apis/metal3.io/v1alpha1/hostfirmwarecomponents
-
GET
: list objects of kind HostFirmwareComponents
-
/apis/metal3.io/v1alpha1/namespaces/{namespace}/hostfirmwarecomponents
-
DELETE
: delete collection of HostFirmwareComponents -
GET
: list objects of kind HostFirmwareComponents -
POST
: create HostFirmwareComponents
-
/apis/metal3.io/v1alpha1/namespaces/{namespace}/hostfirmwarecomponents/{name}
-
DELETE
: delete HostFirmwareComponents -
GET
: read the specified HostFirmwareComponents -
PATCH
: partially update the specified HostFirmwareComponents -
PUT
: replace the specified HostFirmwareComponents
-
/apis/metal3.io/v1alpha1/namespaces/{namespace}/hostfirmwarecomponents/{name}/status
-
GET
: read status of the specified HostFirmwareComponents -
PATCH
: partially update status of the specified HostFirmwareComponents -
PUT
: replace status of the specified HostFirmwareComponents
-
7.2.1. /apis/metal3.io/v1alpha1/hostfirmwarecomponents
- HTTP method
-
GET
- Description
- list objects of kind HostFirmwareComponents
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
7.2.2. /apis/metal3.io/v1alpha1/namespaces/{namespace}/hostfirmwarecomponents
- HTTP method
-
DELETE
- Description
- delete collection of HostFirmwareComponents
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
- HTTP method
-
GET
- Description
- list objects of kind HostFirmwareComponents
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
- HTTP method
-
POST
- Description
- create HostFirmwareComponents
Parameter | Type | Description |
---|---|---|
|
| 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 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. |
Parameter | Type | Description |
---|---|---|
|
|
HTTP code | Reponse body |
---|---|
200 - OK |
|
201 - Created |
|
202 - Accepted |
|
401 - Unauthorized | Empty |
7.2.3. /apis/metal3.io/v1alpha1/namespaces/{namespace}/hostfirmwarecomponents/{name}
Parameter | Type | Description |
---|---|---|
|
| name of the HostFirmwareComponents |
- HTTP method
-
DELETE
- Description
- delete HostFirmwareComponents
Parameter | Type | Description |
---|---|---|
|
| 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 code | Reponse body |
---|---|
200 - OK |
|
202 - Accepted |
|
401 - Unauthorized | Empty |
- HTTP method
-
GET
- Description
- read the specified HostFirmwareComponents
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
- HTTP method
-
PATCH
- Description
- partially update the specified HostFirmwareComponents
Parameter | Type | Description |
---|---|---|
|
| 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 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 code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
- HTTP method
-
PUT
- Description
- replace the specified HostFirmwareComponents
Parameter | Type | Description |
---|---|---|
|
| 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 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. |
Parameter | Type | Description |
---|---|---|
|
|
HTTP code | Reponse body |
---|---|
200 - OK |
|
201 - Created |
|
401 - Unauthorized | Empty |
7.2.4. /apis/metal3.io/v1alpha1/namespaces/{namespace}/hostfirmwarecomponents/{name}/status
Parameter | Type | Description |
---|---|---|
|
| name of the HostFirmwareComponents |
- HTTP method
-
GET
- Description
- read status of the specified HostFirmwareComponents
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
- HTTP method
-
PATCH
- Description
- partially update status of the specified HostFirmwareComponents
Parameter | Type | Description |
---|---|---|
|
| 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 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 code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
- HTTP method
-
PUT
- Description
- replace status of the specified HostFirmwareComponents
Parameter | Type | Description |
---|---|---|
|
| 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 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. |
Parameter | Type | Description |
---|---|---|
|
|
HTTP code | Reponse body |
---|---|
200 - OK |
|
201 - Created |
|
401 - Unauthorized | Empty |
Chapter 8. HostFirmwareSettings [metal3.io/v1alpha1]
- Description
- HostFirmwareSettings is the Schema for the hostfirmwaresettings API.
- Type
-
object
8.1. Specification
Property | Type | Description |
---|---|---|
|
| 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 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 |
| Standard object’s metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata | |
|
| HostFirmwareSettingsSpec defines the desired state of HostFirmwareSettings. |
|
| HostFirmwareSettingsStatus defines the observed state of HostFirmwareSettings. |
8.1.1. .spec
- Description
- HostFirmwareSettingsSpec defines the desired state of HostFirmwareSettings.
- Type
-
object
- Required
-
settings
-
Property | Type | Description |
---|---|---|
|
| Settings are the desired firmware settings stored as name/value pairs. |
8.1.2. .status
- Description
- HostFirmwareSettingsStatus defines the observed state of HostFirmwareSettings.
- Type
-
object
- Required
-
settings
-
Property | Type | Description |
---|---|---|
|
| Track whether settings stored in the spec are valid based on the schema |
|
|
Condition contains details for one aspect of the current state of this API Resource. --- This struct is intended for direct use as an array at the field path .status.conditions. For example, type FooStatus struct{ // Represents the observations of a foo’s current state. // Known .status.conditions.type are: "Available", "Progressing", and "Degraded" // +patchMergeKey=type // +patchStrategy=merge // +listType=map // +listMapKey=type Conditions []metav1.Condition |
|
| Time that the status was last updated |
|
| FirmwareSchema is a reference to the Schema used to describe each FirmwareSetting. By default, this will be a Schema in the same Namespace as the settings but it can be overwritten in the Spec |
|
| Settings are the firmware settings stored as name/value pairs |
8.1.3. .status.conditions
- Description
- Track whether settings stored in the spec are valid based on the schema
- Type
-
array
8.1.4. .status.conditions[]
- Description
-
Condition contains details for one aspect of the current state of this API Resource. --- This struct is intended for direct use as an array at the field path .status.conditions. For example, type FooStatus struct{ // Represents the observations of a foo’s current state. // Known .status.conditions.type are: "Available", "Progressing", and "Degraded" // +patchMergeKey=type // +patchStrategy=merge // +listType=map // +listMapKey=type Conditions []metav1.Condition
json:"conditions,omitempty" patchStrategy:"merge" patchMergeKey:"type" protobuf:"bytes,1,rep,name=conditions"
// other fields } - Type
-
object
- Required
-
lastTransitionTime
-
message
-
reason
-
status
-
type
-
Property | Type | Description |
---|---|---|
|
| lastTransitionTime is the 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 is a human readable message indicating details about the transition. This may be an empty string. |
|
| observedGeneration represents the .metadata.generation that the condition was set based upon. For instance, if .metadata.generation is currently 12, but the .status.conditions[x].observedGeneration is 9, the condition is out of date with respect to the current state of the instance. |
|
| reason contains a programmatic identifier indicating the reason for the condition’s last transition. Producers of specific condition types may define expected values and meanings for this field, and whether the values are considered a guaranteed API. The value should be a CamelCase string. This field may not be empty. |
|
| status of the condition, one of True, False, Unknown. |
|
| 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. The regex it matches is (dns1123SubdomainFmt/)?(qualifiedNameFmt) |
8.1.5. .status.schema
- Description
- FirmwareSchema is a reference to the Schema used to describe each FirmwareSetting. By default, this will be a Schema in the same Namespace as the settings but it can be overwritten in the Spec
- Type
-
object
- Required
-
name
-
namespace
-
Property | Type | Description |
---|---|---|
|
|
|
|
|
|
8.2. API endpoints
The following API endpoints are available:
/apis/metal3.io/v1alpha1/hostfirmwaresettings
-
GET
: list objects of kind HostFirmwareSettings
-
/apis/metal3.io/v1alpha1/namespaces/{namespace}/hostfirmwaresettings
-
DELETE
: delete collection of HostFirmwareSettings -
GET
: list objects of kind HostFirmwareSettings -
POST
: create HostFirmwareSettings
-
/apis/metal3.io/v1alpha1/namespaces/{namespace}/hostfirmwaresettings/{name}
-
DELETE
: delete HostFirmwareSettings -
GET
: read the specified HostFirmwareSettings -
PATCH
: partially update the specified HostFirmwareSettings -
PUT
: replace the specified HostFirmwareSettings
-
/apis/metal3.io/v1alpha1/namespaces/{namespace}/hostfirmwaresettings/{name}/status
-
GET
: read status of the specified HostFirmwareSettings -
PATCH
: partially update status of the specified HostFirmwareSettings -
PUT
: replace status of the specified HostFirmwareSettings
-
8.2.1. /apis/metal3.io/v1alpha1/hostfirmwaresettings
- HTTP method
-
GET
- Description
- list objects of kind HostFirmwareSettings
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
8.2.2. /apis/metal3.io/v1alpha1/namespaces/{namespace}/hostfirmwaresettings
- HTTP method
-
DELETE
- Description
- delete collection of HostFirmwareSettings
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
- HTTP method
-
GET
- Description
- list objects of kind HostFirmwareSettings
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
- HTTP method
-
POST
- Description
- create HostFirmwareSettings
Parameter | Type | Description |
---|---|---|
|
| 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 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. |
Parameter | Type | Description |
---|---|---|
|
|
HTTP code | Reponse body |
---|---|
200 - OK |
|
201 - Created |
|
202 - Accepted |
|
401 - Unauthorized | Empty |
8.2.3. /apis/metal3.io/v1alpha1/namespaces/{namespace}/hostfirmwaresettings/{name}
Parameter | Type | Description |
---|---|---|
|
| name of the HostFirmwareSettings |
- HTTP method
-
DELETE
- Description
- delete HostFirmwareSettings
Parameter | Type | Description |
---|---|---|
|
| 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 code | Reponse body |
---|---|
200 - OK |
|
202 - Accepted |
|
401 - Unauthorized | Empty |
- HTTP method
-
GET
- Description
- read the specified HostFirmwareSettings
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
- HTTP method
-
PATCH
- Description
- partially update the specified HostFirmwareSettings
Parameter | Type | Description |
---|---|---|
|
| 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 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 code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
- HTTP method
-
PUT
- Description
- replace the specified HostFirmwareSettings
Parameter | Type | Description |
---|---|---|
|
| 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 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. |
Parameter | Type | Description |
---|---|---|
|
|
HTTP code | Reponse body |
---|---|
200 - OK |
|
201 - Created |
|
401 - Unauthorized | Empty |
8.2.4. /apis/metal3.io/v1alpha1/namespaces/{namespace}/hostfirmwaresettings/{name}/status
Parameter | Type | Description |
---|---|---|
|
| name of the HostFirmwareSettings |
- HTTP method
-
GET
- Description
- read status of the specified HostFirmwareSettings
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
- HTTP method
-
PATCH
- Description
- partially update status of the specified HostFirmwareSettings
Parameter | Type | Description |
---|---|---|
|
| 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 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 code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
- HTTP method
-
PUT
- Description
- replace status of the specified HostFirmwareSettings
Parameter | Type | Description |
---|---|---|
|
| 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 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. |
Parameter | Type | Description |
---|---|---|
|
|
HTTP code | Reponse body |
---|---|
200 - OK |
|
201 - Created |
|
401 - Unauthorized | Empty |
Chapter 9. Metal3Remediation [infrastructure.cluster.x-k8s.io/v1beta1]
- Description
- Metal3Remediation is the Schema for the metal3remediations API.
- Type
-
object
9.1. Specification
Property | Type | Description |
---|---|---|
|
| 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 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 |
| Standard object’s metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata | |
|
| Metal3RemediationSpec defines the desired state of Metal3Remediation. |
|
| Metal3RemediationStatus defines the observed state of Metal3Remediation. |
9.1.1. .spec
- Description
- Metal3RemediationSpec defines the desired state of Metal3Remediation.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| Strategy field defines remediation strategy. |
9.1.2. .spec.strategy
- Description
- Strategy field defines remediation strategy.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| Sets maximum number of remediation retries. |
|
| Sets the timeout between remediation retries. |
|
| Type of remediation. |
9.1.3. .status
- Description
- Metal3RemediationStatus defines the observed state of Metal3Remediation.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| LastRemediated identifies when the host was last remediated |
|
| Phase represents the current phase of machine remediation. E.g. Pending, Running, Done etc. |
|
| RetryCount can be used as a counter during the remediation. Field can hold number of reboots etc. |
9.2. API endpoints
The following API endpoints are available:
/apis/infrastructure.cluster.x-k8s.io/v1beta1/metal3remediations
-
GET
: list objects of kind Metal3Remediation
-
/apis/infrastructure.cluster.x-k8s.io/v1beta1/namespaces/{namespace}/metal3remediations
-
DELETE
: delete collection of Metal3Remediation -
GET
: list objects of kind Metal3Remediation -
POST
: create a Metal3Remediation
-
/apis/infrastructure.cluster.x-k8s.io/v1beta1/namespaces/{namespace}/metal3remediations/{name}
-
DELETE
: delete a Metal3Remediation -
GET
: read the specified Metal3Remediation -
PATCH
: partially update the specified Metal3Remediation -
PUT
: replace the specified Metal3Remediation
-
/apis/infrastructure.cluster.x-k8s.io/v1beta1/namespaces/{namespace}/metal3remediations/{name}/status
-
GET
: read status of the specified Metal3Remediation -
PATCH
: partially update status of the specified Metal3Remediation -
PUT
: replace status of the specified Metal3Remediation
-
9.2.1. /apis/infrastructure.cluster.x-k8s.io/v1beta1/metal3remediations
- HTTP method
-
GET
- Description
- list objects of kind Metal3Remediation
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
9.2.2. /apis/infrastructure.cluster.x-k8s.io/v1beta1/namespaces/{namespace}/metal3remediations
- HTTP method
-
DELETE
- Description
- delete collection of Metal3Remediation
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
- HTTP method
-
GET
- Description
- list objects of kind Metal3Remediation
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
- HTTP method
-
POST
- Description
- create a Metal3Remediation
Parameter | Type | Description |
---|---|---|
|
| 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 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. |
Parameter | Type | Description |
---|---|---|
|
|
HTTP code | Reponse body |
---|---|
200 - OK |
|
201 - Created |
|
202 - Accepted |
|
401 - Unauthorized | Empty |
9.2.3. /apis/infrastructure.cluster.x-k8s.io/v1beta1/namespaces/{namespace}/metal3remediations/{name}
Parameter | Type | Description |
---|---|---|
|
| name of the Metal3Remediation |
- HTTP method
-
DELETE
- Description
- delete a Metal3Remediation
Parameter | Type | Description |
---|---|---|
|
| 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 code | Reponse body |
---|---|
200 - OK |
|
202 - Accepted |
|
401 - Unauthorized | Empty |
- HTTP method
-
GET
- Description
- read the specified Metal3Remediation
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
- HTTP method
-
PATCH
- Description
- partially update the specified Metal3Remediation
Parameter | Type | Description |
---|---|---|
|
| 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 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 code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
- HTTP method
-
PUT
- Description
- replace the specified Metal3Remediation
Parameter | Type | Description |
---|---|---|
|
| 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 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. |
Parameter | Type | Description |
---|---|---|
|
|
HTTP code | Reponse body |
---|---|
200 - OK |
|
201 - Created |
|
401 - Unauthorized | Empty |
9.2.4. /apis/infrastructure.cluster.x-k8s.io/v1beta1/namespaces/{namespace}/metal3remediations/{name}/status
Parameter | Type | Description |
---|---|---|
|
| name of the Metal3Remediation |
- HTTP method
-
GET
- Description
- read status of the specified Metal3Remediation
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
- HTTP method
-
PATCH
- Description
- partially update status of the specified Metal3Remediation
Parameter | Type | Description |
---|---|---|
|
| 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 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 code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
- HTTP method
-
PUT
- Description
- replace status of the specified Metal3Remediation
Parameter | Type | Description |
---|---|---|
|
| 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 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. |
Parameter | Type | Description |
---|---|---|
|
|
HTTP code | Reponse body |
---|---|
200 - OK |
|
201 - Created |
|
401 - Unauthorized | Empty |
Chapter 10. Metal3RemediationTemplate [infrastructure.cluster.x-k8s.io/v1beta1]
- Description
- Metal3RemediationTemplate is the Schema for the metal3remediationtemplates API.
- Type
-
object
10.1. Specification
Property | Type | Description |
---|---|---|
|
| 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 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 |
| Standard object’s metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata | |
|
| Metal3RemediationTemplateSpec defines the desired state of Metal3RemediationTemplate. |
|
| Metal3RemediationTemplateStatus defines the observed state of Metal3RemediationTemplate. |
10.1.1. .spec
- Description
- Metal3RemediationTemplateSpec defines the desired state of Metal3RemediationTemplate.
- Type
-
object
- Required
-
template
-
Property | Type | Description |
---|---|---|
|
| Metal3RemediationTemplateResource describes the data needed to create a Metal3Remediation from a template. |
10.1.2. .spec.template
- Description
- Metal3RemediationTemplateResource describes the data needed to create a Metal3Remediation from a template.
- Type
-
object
- Required
-
spec
-
Property | Type | Description |
---|---|---|
|
| Spec is the specification of the desired behavior of the Metal3Remediation. |
10.1.3. .spec.template.spec
- Description
- Spec is the specification of the desired behavior of the Metal3Remediation.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| Strategy field defines remediation strategy. |
10.1.4. .spec.template.spec.strategy
- Description
- Strategy field defines remediation strategy.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| Sets maximum number of remediation retries. |
|
| Sets the timeout between remediation retries. |
|
| Type of remediation. |
10.1.5. .status
- Description
- Metal3RemediationTemplateStatus defines the observed state of Metal3RemediationTemplate.
- Type
-
object
- Required
-
status
-
Property | Type | Description |
---|---|---|
|
| Metal3RemediationStatus defines the observed state of Metal3Remediation |
10.1.6. .status.status
- Description
- Metal3RemediationStatus defines the observed state of Metal3Remediation
- Type
-
object
Property | Type | Description |
---|---|---|
|
| LastRemediated identifies when the host was last remediated |
|
| Phase represents the current phase of machine remediation. E.g. Pending, Running, Done etc. |
|
| RetryCount can be used as a counter during the remediation. Field can hold number of reboots etc. |
10.2. API endpoints
The following API endpoints are available:
/apis/infrastructure.cluster.x-k8s.io/v1beta1/metal3remediationtemplates
-
GET
: list objects of kind Metal3RemediationTemplate
-
/apis/infrastructure.cluster.x-k8s.io/v1beta1/namespaces/{namespace}/metal3remediationtemplates
-
DELETE
: delete collection of Metal3RemediationTemplate -
GET
: list objects of kind Metal3RemediationTemplate -
POST
: create a Metal3RemediationTemplate
-
/apis/infrastructure.cluster.x-k8s.io/v1beta1/namespaces/{namespace}/metal3remediationtemplates/{name}
-
DELETE
: delete a Metal3RemediationTemplate -
GET
: read the specified Metal3RemediationTemplate -
PATCH
: partially update the specified Metal3RemediationTemplate -
PUT
: replace the specified Metal3RemediationTemplate
-
/apis/infrastructure.cluster.x-k8s.io/v1beta1/namespaces/{namespace}/metal3remediationtemplates/{name}/status
-
GET
: read status of the specified Metal3RemediationTemplate -
PATCH
: partially update status of the specified Metal3RemediationTemplate -
PUT
: replace status of the specified Metal3RemediationTemplate
-
10.2.1. /apis/infrastructure.cluster.x-k8s.io/v1beta1/metal3remediationtemplates
- HTTP method
-
GET
- Description
- list objects of kind Metal3RemediationTemplate
HTTP code | Reponse body |
---|---|
200 - OK | |
401 - Unauthorized | Empty |
10.2.2. /apis/infrastructure.cluster.x-k8s.io/v1beta1/namespaces/{namespace}/metal3remediationtemplates
- HTTP method
-
DELETE
- Description
- delete collection of Metal3RemediationTemplate
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
- HTTP method
-
GET
- Description
- list objects of kind Metal3RemediationTemplate
HTTP code | Reponse body |
---|---|
200 - OK | |
401 - Unauthorized | Empty |
- HTTP method
-
POST
- Description
- create a Metal3RemediationTemplate
Parameter | Type | Description |
---|---|---|
|
| 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 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. |
Parameter | Type | Description |
---|---|---|
|
|
HTTP code | Reponse body |
---|---|
200 - OK |
|
201 - Created |
|
202 - Accepted |
|
401 - Unauthorized | Empty |
10.2.3. /apis/infrastructure.cluster.x-k8s.io/v1beta1/namespaces/{namespace}/metal3remediationtemplates/{name}
Parameter | Type | Description |
---|---|---|
|
| name of the Metal3RemediationTemplate |
- HTTP method
-
DELETE
- Description
- delete a Metal3RemediationTemplate
Parameter | Type | Description |
---|---|---|
|
| 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 code | Reponse body |
---|---|
200 - OK |
|
202 - Accepted |
|
401 - Unauthorized | Empty |
- HTTP method
-
GET
- Description
- read the specified Metal3RemediationTemplate
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
- HTTP method
-
PATCH
- Description
- partially update the specified Metal3RemediationTemplate
Parameter | Type | Description |
---|---|---|
|
| 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 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 code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
- HTTP method
-
PUT
- Description
- replace the specified Metal3RemediationTemplate
Parameter | Type | Description |
---|---|---|
|
| 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 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. |
Parameter | Type | Description |
---|---|---|
|
|
HTTP code | Reponse body |
---|---|
200 - OK |
|
201 - Created |
|
401 - Unauthorized | Empty |
10.2.4. /apis/infrastructure.cluster.x-k8s.io/v1beta1/namespaces/{namespace}/metal3remediationtemplates/{name}/status
Parameter | Type | Description |
---|---|---|
|
| name of the Metal3RemediationTemplate |
- HTTP method
-
GET
- Description
- read status of the specified Metal3RemediationTemplate
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
- HTTP method
-
PATCH
- Description
- partially update status of the specified Metal3RemediationTemplate
Parameter | Type | Description |
---|---|---|
|
| 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 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 code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
- HTTP method
-
PUT
- Description
- replace status of the specified Metal3RemediationTemplate
Parameter | Type | Description |
---|---|---|
|
| 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 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. |
Parameter | Type | Description |
---|---|---|
|
|
HTTP code | Reponse body |
---|---|
200 - OK |
|
201 - Created |
|
401 - Unauthorized | Empty |
Chapter 11. PreprovisioningImage [metal3.io/v1alpha1]
- Description
- PreprovisioningImage is the Schema for the preprovisioningimages API.
- Type
-
object
11.1. Specification
Property | Type | Description |
---|---|---|
|
| 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 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 |
| Standard object’s metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata | |
|
| PreprovisioningImageSpec defines the desired state of PreprovisioningImage. |
|
| PreprovisioningImageStatus defines the observed state of PreprovisioningImage. |
11.1.1. .spec
- Description
- PreprovisioningImageSpec defines the desired state of PreprovisioningImage.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| acceptFormats is a list of acceptable image formats. |
|
| architecture is the processor architecture for which to build the image. |
|
| networkDataName is the name of a Secret in the local namespace that contains network data to build in to the image. |
11.1.2. .status
- Description
- PreprovisioningImageStatus defines the observed state of PreprovisioningImage.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| architecture is the processor architecture for which the image is built |
|
| conditions describe the state of the built image |
|
|
Condition contains details for one aspect of the current state of this API Resource. --- This struct is intended for direct use as an array at the field path .status.conditions. For example, type FooStatus struct{ // Represents the observations of a foo’s current state. // Known .status.conditions.type are: "Available", "Progressing", and "Degraded" // +patchMergeKey=type // +patchStrategy=merge // +listType=map // +listMapKey=type Conditions []metav1.Condition |
|
| extraKernelParams is a string with extra parameters to pass to the kernel when booting the image over network. Only makes sense for initrd images. |
|
| format is the type of image that is available at the download url: either iso or initrd. |
|
| imageUrl is the URL from which the built image can be downloaded. |
|
| kernelUrl is the URL from which the kernel of the image can be downloaded. Only makes sense for initrd images. |
|
| networkData is a reference to the version of the Secret containing the network data used to build the image. |
11.1.3. .status.conditions
- Description
- conditions describe the state of the built image
- Type
-
array
11.1.4. .status.conditions[]
- Description
-
Condition contains details for one aspect of the current state of this API Resource. --- This struct is intended for direct use as an array at the field path .status.conditions. For example, type FooStatus struct{ // Represents the observations of a foo’s current state. // Known .status.conditions.type are: "Available", "Progressing", and "Degraded" // +patchMergeKey=type // +patchStrategy=merge // +listType=map // +listMapKey=type Conditions []metav1.Condition
json:"conditions,omitempty" patchStrategy:"merge" patchMergeKey:"type" protobuf:"bytes,1,rep,name=conditions"
// other fields } - Type
-
object
- Required
-
lastTransitionTime
-
message
-
reason
-
status
-
type
-
Property | Type | Description |
---|---|---|
|
| lastTransitionTime is the 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 is a human readable message indicating details about the transition. This may be an empty string. |
|
| observedGeneration represents the .metadata.generation that the condition was set based upon. For instance, if .metadata.generation is currently 12, but the .status.conditions[x].observedGeneration is 9, the condition is out of date with respect to the current state of the instance. |
|
| reason contains a programmatic identifier indicating the reason for the condition’s last transition. Producers of specific condition types may define expected values and meanings for this field, and whether the values are considered a guaranteed API. The value should be a CamelCase string. This field may not be empty. |
|
| status of the condition, one of True, False, Unknown. |
|
| 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. The regex it matches is (dns1123SubdomainFmt/)?(qualifiedNameFmt) |
11.1.5. .status.networkData
- Description
- networkData is a reference to the version of the Secret containing the network data used to build the image.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| |
|
|
11.2. API endpoints
The following API endpoints are available:
/apis/metal3.io/v1alpha1/preprovisioningimages
-
GET
: list objects of kind PreprovisioningImage
-
/apis/metal3.io/v1alpha1/namespaces/{namespace}/preprovisioningimages
-
DELETE
: delete collection of PreprovisioningImage -
GET
: list objects of kind PreprovisioningImage -
POST
: create a PreprovisioningImage
-
/apis/metal3.io/v1alpha1/namespaces/{namespace}/preprovisioningimages/{name}
-
DELETE
: delete a PreprovisioningImage -
GET
: read the specified PreprovisioningImage -
PATCH
: partially update the specified PreprovisioningImage -
PUT
: replace the specified PreprovisioningImage
-
/apis/metal3.io/v1alpha1/namespaces/{namespace}/preprovisioningimages/{name}/status
-
GET
: read status of the specified PreprovisioningImage -
PATCH
: partially update status of the specified PreprovisioningImage -
PUT
: replace status of the specified PreprovisioningImage
-
11.2.1. /apis/metal3.io/v1alpha1/preprovisioningimages
- HTTP method
-
GET
- Description
- list objects of kind PreprovisioningImage
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
11.2.2. /apis/metal3.io/v1alpha1/namespaces/{namespace}/preprovisioningimages
- HTTP method
-
DELETE
- Description
- delete collection of PreprovisioningImage
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
- HTTP method
-
GET
- Description
- list objects of kind PreprovisioningImage
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
- HTTP method
-
POST
- Description
- create a PreprovisioningImage
Parameter | Type | Description |
---|---|---|
|
| 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 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. |
Parameter | Type | Description |
---|---|---|
|
|
HTTP code | Reponse body |
---|---|
200 - OK |
|
201 - Created |
|
202 - Accepted |
|
401 - Unauthorized | Empty |
11.2.3. /apis/metal3.io/v1alpha1/namespaces/{namespace}/preprovisioningimages/{name}
Parameter | Type | Description |
---|---|---|
|
| name of the PreprovisioningImage |
- HTTP method
-
DELETE
- Description
- delete a PreprovisioningImage
Parameter | Type | Description |
---|---|---|
|
| 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 code | Reponse body |
---|---|
200 - OK |
|
202 - Accepted |
|
401 - Unauthorized | Empty |
- HTTP method
-
GET
- Description
- read the specified PreprovisioningImage
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
- HTTP method
-
PATCH
- Description
- partially update the specified PreprovisioningImage
Parameter | Type | Description |
---|---|---|
|
| 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 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 code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
- HTTP method
-
PUT
- Description
- replace the specified PreprovisioningImage
Parameter | Type | Description |
---|---|---|
|
| 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 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. |
Parameter | Type | Description |
---|---|---|
|
|
HTTP code | Reponse body |
---|---|
200 - OK |
|
201 - Created |
|
401 - Unauthorized | Empty |
11.2.4. /apis/metal3.io/v1alpha1/namespaces/{namespace}/preprovisioningimages/{name}/status
Parameter | Type | Description |
---|---|---|
|
| name of the PreprovisioningImage |
- HTTP method
-
GET
- Description
- read status of the specified PreprovisioningImage
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
- HTTP method
-
PATCH
- Description
- partially update status of the specified PreprovisioningImage
Parameter | Type | Description |
---|---|---|
|
| 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 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 code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
- HTTP method
-
PUT
- Description
- replace status of the specified PreprovisioningImage
Parameter | Type | Description |
---|---|---|
|
| 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 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. |
Parameter | Type | Description |
---|---|---|
|
|
HTTP code | Reponse body |
---|---|
200 - OK |
|
201 - Created |
|
401 - Unauthorized | Empty |
Chapter 12. Provisioning [metal3.io/v1alpha1]
- Description
- Provisioning contains configuration used by the Provisioning service (Ironic) to provision baremetal hosts. Provisioning is created by the OpenShift installer using admin or user provided information about the provisioning network and the NIC on the server that can be used to PXE boot it. This CR is a singleton, created by the installer and currently only consumed by the cluster-baremetal-operator to bring up and update containers in a metal3 cluster.
- Type
-
object
12.1. Specification
Property | Type | Description |
---|---|---|
|
| 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 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 |
| Standard object’s metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata | |
|
| ProvisioningSpec defines the desired state of Provisioning |
|
| ProvisioningStatus defines the observed state of Provisioning |
12.1.1. .spec
- Description
- ProvisioningSpec defines the desired state of Provisioning
- Type
-
object
Property | Type | Description |
---|---|---|
|
| BootIsoSource provides a way to set the location where the iso image to boot the nodes will be served from. By default the boot iso image is cached locally and served from the Provisioning service (Ironic) nodes using an auxiliary httpd server. If the boot iso image is already served by an httpd server, setting this option to http allows to directly provide the image from there; in this case, the network (either internal or external) where the httpd server that hosts the boot iso is needs to be accessible by the metal3 pod. |
|
| DisableVirtualMediaTLS turns off TLS on the virtual media server, which may be required for hardware that cannot accept HTTPS links. |
|
| PreprovisioningOSDownloadURLs is set of CoreOS Live URLs that would be necessary to provision a worker either using virtual media or PXE. |
|
| ProvisioningDHCPExternal indicates whether the DHCP server for IP addresses in the provisioning DHCP range is present within the metal3 cluster or external to it. This field is being deprecated in favor of provisioningNetwork. |
|
| ProvisioningDHCPRange needs to be interpreted along with ProvisioningDHCPExternal. If the value of provisioningDHCPExternal is set to False, then ProvisioningDHCPRange represents the range of IP addresses that the DHCP server running within the metal3 cluster can use while provisioning baremetal servers. If the value of ProvisioningDHCPExternal is set to True, then the value of ProvisioningDHCPRange will be ignored. When the value of ProvisioningDHCPExternal is set to False, indicating an internal DHCP server and the value of ProvisioningDHCPRange is not set, then the DHCP range is taken to be the default range which goes from .10 to .100 of the ProvisioningNetworkCIDR. This is the only value in all of the Provisioning configuration that can be changed after the installer has created the CR. This value needs to be two comma sererated IP addresses within the ProvisioningNetworkCIDR where the 1st address represents the start of the range and the 2nd address represents the last usable address in the range. |
|
| ProvisioningDNS allows sending the DNS information via DHCP on the provisionig network. It is off by default since the Provisioning service itself (Ironic) does not require DNS, but it may be useful for layered products (e.g. ZTP). |
|
| ProvisioningIP is the IP address assigned to the provisioningInterface of the baremetal server. This IP address should be within the provisioning subnet, and outside of the DHCP range. |
|
| ProvisioningInterface is the name of the network interface on a baremetal server to the provisioning network. It can have values like eth1 or ens3. |
|
| ProvisioningMacAddresses is a list of mac addresses of network interfaces on a baremetal server to the provisioning network. Use this instead of ProvisioningInterface to allow interfaces of different names. If not provided it will be populated by the BMH.Spec.BootMacAddress of each master. |
|
|
ProvisioningNetwork provides a way to indicate the state of the underlying network configuration for the provisioning network. This field can have one of the following values - |
|
| ProvisioningNetworkCIDR is the network on which the baremetal nodes are provisioned. The provisioningIP and the IPs in the dhcpRange all come from within this network. When using IPv6 and in a network managed by the Baremetal IPI solution this cannot be a network larger than a /64. |
|
| ProvisioningOSDownloadURL is the location from which the OS Image used to boot baremetal host machines can be downloaded by the metal3 cluster. |
|
| VirtualMediaViaExternalNetwork flag when set to "true" allows for workers to boot via Virtual Media and contact metal3 over the External Network. When the flag is set to "false" (which is the default), virtual media deployments can still happen based on the configuration specified in the ProvisioningNetwork i.e when in Disabled mode, over the External Network and over Provisioning Network when in Managed mode. PXE deployments will always use the Provisioning Network and will not be affected by this flag. |
|
| WatchAllNamespaces provides a way to explicitly allow use of this Provisioning configuration across all Namespaces. It is an optional configuration which defaults to false and in that state will be used to provision baremetal hosts in only the openshift-machine-api namespace. When set to true, this provisioning configuration would be used for baremetal hosts across all namespaces. |
12.1.2. .spec.preProvisioningOSDownloadURLs
- Description
- PreprovisioningOSDownloadURLs is set of CoreOS Live URLs that would be necessary to provision a worker either using virtual media or PXE.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| InitramfsURL Image URL to be used for PXE deployments |
|
| IsoURL Image URL to be used for Live ISO deployments |
|
| KernelURL is an Image URL to be used for PXE deployments |
|
| RootfsURL Image URL to be used for PXE deployments |
12.1.3. .status
- Description
- ProvisioningStatus defines the observed state of Provisioning
- Type
-
object
Property | Type | Description |
---|---|---|
|
| conditions is a list of conditions and their status |
|
| OperatorCondition is just the standard condition fields. |
|
| generations are used to determine when an item needs to be reconciled or has changed in a way that needs a reaction. |
|
| GenerationStatus keeps track of the generation for a given resource so that decisions about forced updates can be made. |
|
| observedGeneration is the last generation change you’ve dealt with |
|
| readyReplicas indicates how many replicas are ready and at the desired state |
|
| version is the level this availability applies to |
12.1.4. .status.conditions
- Description
- conditions is a list of conditions and their status
- Type
-
array
12.1.5. .status.conditions[]
- Description
- OperatorCondition is just the standard condition fields.
- Type
-
object
- Required
-
type
-
Property | Type | Description |
---|---|---|
|
| |
|
| |
|
| |
|
| |
|
|
12.1.6. .status.generations
- Description
- generations are used to determine when an item needs to be reconciled or has changed in a way that needs a reaction.
- Type
-
array
12.1.7. .status.generations[]
- Description
- GenerationStatus keeps track of the generation for a given resource so that decisions about forced updates can be made.
- Type
-
object
Property | Type | Description |
---|---|---|
|
| group is the group of the thing you’re tracking |
|
| hash is an optional field set for resources without generation that are content sensitive like secrets and configmaps |
|
| lastGeneration is the last generation of the workload controller involved |
|
| name is the name of the thing you’re tracking |
|
| namespace is where the thing you’re tracking is |
|
| resource is the resource type of the thing you’re tracking |
12.2. API endpoints
The following API endpoints are available:
/apis/metal3.io/v1alpha1/provisionings
-
DELETE
: delete collection of Provisioning -
GET
: list objects of kind Provisioning -
POST
: create a Provisioning
-
/apis/metal3.io/v1alpha1/provisionings/{name}
-
DELETE
: delete a Provisioning -
GET
: read the specified Provisioning -
PATCH
: partially update the specified Provisioning -
PUT
: replace the specified Provisioning
-
/apis/metal3.io/v1alpha1/provisionings/{name}/status
-
GET
: read status of the specified Provisioning -
PATCH
: partially update status of the specified Provisioning -
PUT
: replace status of the specified Provisioning
-
12.2.1. /apis/metal3.io/v1alpha1/provisionings
- HTTP method
-
DELETE
- Description
- delete collection of Provisioning
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
- HTTP method
-
GET
- Description
- list objects of kind Provisioning
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
- HTTP method
-
POST
- Description
- create a Provisioning
Parameter | Type | Description |
---|---|---|
|
| 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 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. |
Parameter | Type | Description |
---|---|---|
|
|
HTTP code | Reponse body |
---|---|
200 - OK |
|
201 - Created |
|
202 - Accepted |
|
401 - Unauthorized | Empty |
12.2.2. /apis/metal3.io/v1alpha1/provisionings/{name}
Parameter | Type | Description |
---|---|---|
|
| name of the Provisioning |
- HTTP method
-
DELETE
- Description
- delete a Provisioning
Parameter | Type | Description |
---|---|---|
|
| 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 code | Reponse body |
---|---|
200 - OK |
|
202 - Accepted |
|
401 - Unauthorized | Empty |
- HTTP method
-
GET
- Description
- read the specified Provisioning
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
- HTTP method
-
PATCH
- Description
- partially update the specified Provisioning
Parameter | Type | Description |
---|---|---|
|
| 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 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 code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
- HTTP method
-
PUT
- Description
- replace the specified Provisioning
Parameter | Type | Description |
---|---|---|
|
| 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 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. |
Parameter | Type | Description |
---|---|---|
|
|
HTTP code | Reponse body |
---|---|
200 - OK |
|
201 - Created |
|
401 - Unauthorized | Empty |
12.2.3. /apis/metal3.io/v1alpha1/provisionings/{name}/status
Parameter | Type | Description |
---|---|---|
|
| name of the Provisioning |
- HTTP method
-
GET
- Description
- read status of the specified Provisioning
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
- HTTP method
-
PATCH
- Description
- partially update status of the specified Provisioning
Parameter | Type | Description |
---|---|---|
|
| 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 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 code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized | Empty |
- HTTP method
-
PUT
- Description
- replace status of the specified Provisioning
Parameter | Type | Description |
---|---|---|
|
| 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 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. |
Parameter | Type | Description |
---|---|---|
|
|
HTTP code | Reponse body |
---|---|
200 - OK |
|
201 - Created |
|
401 - Unauthorized | Empty |
Legal Notice
Copyright © 2024 Red Hat, Inc.
OpenShift documentation is licensed under the Apache License 2.0 (https://www.apache.org/licenses/LICENSE-2.0).
Modified versions must remove all Red Hat trademarks.
Portions adapted from https://github.com/kubernetes-incubator/service-catalog/ with modifications by Red Hat.
Red Hat, Red Hat Enterprise Linux, the Red Hat logo, the Shadowman logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries.
Linux® is the registered trademark of Linus Torvalds in the United States and other countries.
Java® is a registered trademark of Oracle and/or its affiliates.
XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries.
MySQL® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
Node.js® is an official trademark of Joyent. Red Hat Software Collections is not formally related to or endorsed by the official Joyent Node.js open source or commercial project.
The OpenStack® Word Mark and OpenStack logo are either registered trademarks/service marks or trademarks/service marks of the OpenStack Foundation, in the United States and other countries and are used with the OpenStack Foundation’s permission. We are not affiliated with, endorsed or sponsored by the OpenStack Foundation, or the OpenStack community.
All other trademarks are the property of their respective owners.