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 |