Device is the Schema for the Devices API.
Type
CRD
Group
metal.equinix.jet.crossplane.io
Version
v1alpha1
apiVersion: metal.equinix.jet.crossplane.io/v1alpha1
kind: Device
DeviceSpec defines the desired state of Device
No description provided.
Behavioral overrides that change how the resource handles certain attribute updates. See Behavior below for more details.
List of attributes that are allowed to change without recreating the instance. Supported attributes: custom_data, user_data" List of attributes that are allowed to change without recreating the instance. Supported attributes: custom_data, user_data
A string of the desired Custom Data for the device. By default, changing this attribute will cause the provider to destroy and recreate your device. If reinstall is specified or behavior.allow_changes includes "custom_data", the device will be updated in-place instead of recreated. A string of the desired Custom Data for the device. By default, changing this attribute will cause the provider to destroy and recreate your device. If reinstall is specified or behavior.allow_changes includes "custom_data", the device will be updated in-place instead of recreated.
(Deprecated) List of facility codes with deployment preferences. Equinix Metal API will go through the list and will deploy your device to first facility with free capacity. List items must be facility codes or any (a wildcard). To find the facility code, visit Facilities API docs, set your API auth token in the top of the page and see JSON from the API response. Conflicts with metro. Use metro instead; read the facility to metro migration guide List of facility codes with deployment preferences. Equinix Metal API will go through the list and will deploy your device to first facility with free capacity. List items must be facility codes or any (a wildcard). To find the facility code, visit Facilities API docs, set your API auth token in the top of the page and see JSON from the API response. Conflicts with metro
A list of IP address types for the device. See IP address below for more details. A list of IP address types for the device (structure is documented below)
List of UUIDs of IP block reservations from which the public IPv4 address should be taken. IDs of reservations to pick the blocks from
Reference to a Project to populate projectId.
Policies for referencing.
Selector for a Project to populate projectId.
Policies for selection.
Array of IDs of the project SSH keys which should be added to the device. If you specify this array, only the listed project SSH keys (and any SSH keys for the users specified in user_ssh_key_ids) will be added. If no SSH keys are specified (both user_ssh_keys_ids and project_ssh_key_ids are empty lists or omitted), all parent project keys, parent project members keys and organization members keys will be included. Project SSH keys can be created with the equinix_metal_project_ssh_key resource. Array of IDs of the project SSH keys which should be added to the device. If you specify this array, only the listed project SSH keys (and any SSH keys for the users specified in user_ssh_key_ids) will be added. If no SSH keys are specified (both user_ssh_keys_ids and project_ssh_key_ids are empty lists or omitted), all parent project keys, parent project members keys and organization members keys will be included. Project SSH keys can be created with the equinix_metal_project_ssh_key resource
Whether the device should be reinstalled instead of destroyed when modifying user_data, custom_data, or operating system. See Reinstall below for more details.
Tags attached to the device. Tags attached to the device
A string of the desired User Data for the device. By default, changing this attribute will cause the provider to destroy and recreate your device. If reinstall is specified or behavior.allow_changes includes "user_data", the device will be updated in-place instead of recreated. A string of the desired User Data for the device. By default, changing this attribute will cause the provider to destroy and recreate your device. If reinstall is specified or behavior.allow_changes includes "user_data", the device will be updated in-place instead of recreated.
Array of IDs of the users whose SSH keys should be added to the device. If you specify this array, only the listed users' SSH keys (and any project SSH keys specified in project_ssh_key_ids) will be added. If no SSH keys are specified (both user_ssh_keys_ids and project_ssh_key_ids are empty lists or omitted), all parent project keys, parent project members keys and organization members keys will be included. User SSH keys can be created with the equinix_metal_ssh_key resource. Array of IDs of the users whose SSH keys should be added to the device. If you specify this array, only the listed users' SSH keys (and any project SSH keys specified in project_ssh_key_ids) will be added. If no SSH keys are specified (both user_ssh_keys_ids and project_ssh_key_ids are empty lists or omitted), all parent project keys, parent project members keys and organization members keys will be included. User SSH keys can be created with the equinix_metal_ssh_key resource
ProviderConfigReference specifies how the provider that will be used to create, observe, update, and delete this managed resource should be configured.
Policies for referencing.
ProviderReference specifies the provider that will be used to create, observe, update, and delete this managed resource. Deprecated: Please use ProviderConfigReference, i.e. providerConfigRef
Policies for referencing.
PublishConnectionDetailsTo specifies the connection secret config which contains a name, metadata and a reference to secret store config to which any connection details for this managed resource should be written. Connection details frequently include the endpoint, username, and password required to connect to the managed resource.
WriteConnectionSecretToReference specifies the namespace and name of a Secret to which any connection details for this managed resource should be written. Connection details frequently include the endpoint, username, and password required to connect to the managed resource. This field is planned to be replaced in a future release in favor of PublishConnectionDetailsTo. Currently, both could be set independently and connection details would be published to both without affecting each other.
DeviceStatus defines the observed state of Device.
No description provided.
The device's private and public IP (v4 and v6) network details. See Network Attribute below for more details. The device's private and public IP (v4 and v6) network details. When a device is run without any special network configuration, it will have 3 addresses: public ipv4, private ipv4 and ipv6
List of IDs of SSH keys deployed in the device, can be both user and project SSH keys. List of IDs of SSH keys deployed in the device, can be both user and project SSH keys
Conditions of the resource.
upjet-example
apiVersion: metal.equinix.jet.crossplane.io/v1alpha1
kind: Device
metadata:
name: upjet-example
spec:
forProvider:
billingCycle: hourly
hostname: upjet-example
metro: da
operatingSystem: ubuntu_20_04
plan: t3.small.x86
projectIdRef:
name: upjet-example-project
tags:
- crossplane
providerConfigRef:
name: default
writeConnectionSecretToRef:
name: upjet-example
namespace: crossplane-system
© 2022 Upbound, Inc.
Discover the building blocksfor your internal cloud platform.