HardwareData is the Schema for the hardwaredata api.
HardwareData is the Schema for the hardwaredata api.
object
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. |
HardwareDataSpec defines the desired state of HardwareData.
object
Property | Type | Description |
---|---|---|
|
|
The hardware discovered on the host during its inspection. |
The hardware discovered on the host during its inspection.
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. |
CPU describes one processor on the host.
object
Property | Type | Description |
---|---|---|
|
|
|
|
|
ClockSpeed is a clock speed in MHz |
|
|
|
|
|
|
|
|
Firmware describes the firmware on the host.
object
Property | Type | Description |
---|---|---|
|
|
The BIOS for this firmware |
The BIOS for this firmware
object
Property | Type | Description |
---|---|---|
|
|
The release/build date for this BIOS |
|
|
The vendor name for this BIOS |
|
|
The version of the BIOS |
NIC describes one network interface on the host.
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. |
VLAN represents the name and ID of a VLAN.
object
Property | Type | Description |
---|---|---|
|
|
VLANID is a 12-bit 802.1Q VLAN identifier |
|
|
Storage describes one storage device (disk, SSD, etc.) on the host.
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 |
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
GET
list objects of kind HardwareData
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized |
Empty |
DELETE
delete collection of HardwareData
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized |
Empty |
GET
list objects of kind HardwareData
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized |
Empty |
POST
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 |
Parameter | Type | Description |
---|---|---|
|
|
name of the HardwareData |
DELETE
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 |
GET
read the specified HardwareData
HTTP code | Reponse body |
---|---|
200 - OK |
|
401 - Unauthorized |
Empty |
PATCH
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 |
PUT
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 |