Instance is the Schema for the Instances API. Manages a Linode instance.
Type
CRD
Group
instance.linode.upbound.io
Version
v1alpha1
apiVersion: instance.linode.upbound.io/v1alpha1
kind: Instance
InstanceSpec defines the desired state of Instance
No description provided.
Configuration options for alert triggers on this Linode.
A list of SSH public keys to deploy for the root user on the newly created Linode. This value can not be imported. Changing A list of SSH public keys to deploy for the root user on the newly created Linode. Only accepted if 'image' is provided.
A list of Linode usernames. If the usernames have associated SSH keys, the keys will be appended to the root user's ~/.ssh/authorized_keys file automatically. This value can not be imported. Changing
A list of Linode usernames. If the usernames have associated SSH keys, the keys will be appended to the root user's ~/.ssh/authorized_keys file automatically. Only accepted if 'image' is provided.
block Configuration profiles define the VM settings and boot behavior of the Linode Instance.
A list of disk or volume attachments for this config. If the boot_config_label omits a devices block, the Linode will not be booted. Device sda-sdh can be either a Disk or Volume identified by disk_label or volume_id. Only one type per slot allowed.
The SDA-SDH slots, represent the Linux block device nodes for the first 8 disks attached to the Linode. Each device must be suplied sequentially. The device can be either a Disk or a Volume identified by disk_label or volume_id. Only one disk identifier is permitted per slot. Devices mapped from sde through sdh are unavailable in "fullvirt" virt_mode. Device can be either a Disk or Volume identified by disk_id or volume_id. Only one type per slot allowed.
(Options) Helpers enabled when booting to this Linode Config. Helpers enabled when booting to this Linode Config.
An array of Network Interfaces for this Linode’s Configuration Profile.
IPv4 CIDR VPC Subnet ranges that are routed to this Interface. IPv6 ranges are also available to select participants in the Beta program. List of VPC IPs or IP ranges inside the VPC subnet.
This Linode's IPv4 Addresses. Each Linode is assigned a single public IPv4 address upon creation, and may get a single private IPv4 address if needed. You may need to open a support ticket to get additional IPv4 addresses. The IPv4 configuration of the VPC interface.This attribute is only allowed for VPC interfaces.
The amount of storage space, in GB. this Linode has access to. A typical Linode will divide this space between a primary disk with an image deployed to it, and a swap disk, usually 512 MB. This is the default configuration created when deploying a Linode with an image through POST /linode/instances.
A list of SSH public keys to deploy for the root user on the newly created Linode. This value can not be imported. Changing A list of SSH public keys to deploy for the root user on the newly created Linode. Only accepted if 'image' is provided.
A list of Linode usernames. If the usernames have associated SSH keys, the keys will be appended to the root user's ~/.ssh/authorized_keys file automatically. This value can not be imported. Changing
A list of Linode usernames. If the usernames have associated SSH keys, the keys will be appended to the root user's ~/.ssh/authorized_keys file automatically. Only accepted if 'image' is provided.
An object containing responses to any User Defined Fields present in the StackScript being deployed to this Linode. Only accepted if 'stackscript_id' is given. The required values depend on the StackScript being deployed. This value can not be imported. Changing An object containing responses to any User Defined Fields present in the StackScript being deployed to this Linode. Only accepted if 'stackscript_id' is given. The required values depend on the StackScript being deployed.
An array of Network Interfaces for this Linode to be created with. If an explicit config or disk is defined, interfaces must be declared in the config block.
IPv4 CIDR VPC Subnet ranges that are routed to this Interface. IPv6 ranges are also available to select participants in the Beta program. List of VPC IPs or IP ranges inside the VPC subnet.
This Linode's IPv4 Addresses. Each Linode is assigned a single public IPv4 address upon creation, and may get a single private IPv4 address if needed. You may need to open a support ticket to get additional IPv4 addresses. The IPv4 configuration of the VPC interface.This attribute is only allowed for VPC interfaces.
Information about the Placement Group this Linode is assigned to. NOTE: Placement Groups may not currently be available to all users. Fields related to the Placement Group this instance is assigned to.
A set of IPv4 addresses to be shared with the Instance. These IP addresses can be both private and public, but must be in the same region as the instance. A set of IPv4 addresses to share with this Linode.
An object containing responses to any User Defined Fields present in the StackScript being deployed to this Linode. Only accepted if 'stackscript_id' is given. The required values depend on the StackScript being deployed. This value can not be imported. Changing An object containing responses to any User Defined Fields present in the StackScript being deployed to this Linode. Only accepted if 'stackscript_id' is given. The required values depend on the StackScript being deployed.
Reference to a Stackscript in stackscript to populate stackscriptId.
Policies for referencing.
Selector for a Stackscript in stackscript to populate stackscriptId.
Policies for selection.
A list of tags applied to this object. Tags are case-insensitive and are for organizational purposes only. An array of tags applied to this object. Tags are for organizational purposes only.
THIS IS A BETA FIELD. It will be honored unless the Management Policies feature flag is disabled. InitProvider holds the same fields as ForProvider, with the exception of Identifier and other resource reference fields. The fields that are in InitProvider are merged into ForProvider when the resource is created. The same fields are also added to the terraform ignore_changes hook, to avoid updating them after creation. This is useful for fields that are required on creation, but we do not desire to update them after creation, for example because of an external controller is managing them, like an autoscaler.
Configuration options for alert triggers on this Linode.
A list of SSH public keys to deploy for the root user on the newly created Linode. This value can not be imported. Changing A list of SSH public keys to deploy for the root user on the newly created Linode. Only accepted if 'image' is provided.
A list of Linode usernames. If the usernames have associated SSH keys, the keys will be appended to the root user's ~/.ssh/authorized_keys file automatically. This value can not be imported. Changing
A list of Linode usernames. If the usernames have associated SSH keys, the keys will be appended to the root user's ~/.ssh/authorized_keys file automatically. Only accepted if 'image' is provided.
block Configuration profiles define the VM settings and boot behavior of the Linode Instance.
A list of disk or volume attachments for this config. If the boot_config_label omits a devices block, the Linode will not be booted. Device sda-sdh can be either a Disk or Volume identified by disk_label or volume_id. Only one type per slot allowed.
The SDA-SDH slots, represent the Linux block device nodes for the first 8 disks attached to the Linode. Each device must be suplied sequentially. The device can be either a Disk or a Volume identified by disk_label or volume_id. Only one disk identifier is permitted per slot. Devices mapped from sde through sdh are unavailable in "fullvirt" virt_mode. Device can be either a Disk or Volume identified by disk_id or volume_id. Only one type per slot allowed.
(Options) Helpers enabled when booting to this Linode Config. Helpers enabled when booting to this Linode Config.
An array of Network Interfaces for this Linode’s Configuration Profile.
IPv4 CIDR VPC Subnet ranges that are routed to this Interface. IPv6 ranges are also available to select participants in the Beta program. List of VPC IPs or IP ranges inside the VPC subnet.
This Linode's IPv4 Addresses. Each Linode is assigned a single public IPv4 address upon creation, and may get a single private IPv4 address if needed. You may need to open a support ticket to get additional IPv4 addresses. The IPv4 configuration of the VPC interface.This attribute is only allowed for VPC interfaces.
The amount of storage space, in GB. this Linode has access to. A typical Linode will divide this space between a primary disk with an image deployed to it, and a swap disk, usually 512 MB. This is the default configuration created when deploying a Linode with an image through POST /linode/instances.
A list of SSH public keys to deploy for the root user on the newly created Linode. This value can not be imported. Changing A list of SSH public keys to deploy for the root user on the newly created Linode. Only accepted if 'image' is provided.
A list of Linode usernames. If the usernames have associated SSH keys, the keys will be appended to the root user's ~/.ssh/authorized_keys file automatically. This value can not be imported. Changing
A list of Linode usernames. If the usernames have associated SSH keys, the keys will be appended to the root user's ~/.ssh/authorized_keys file automatically. Only accepted if 'image' is provided.
An array of Network Interfaces for this Linode to be created with. If an explicit config or disk is defined, interfaces must be declared in the config block.
IPv4 CIDR VPC Subnet ranges that are routed to this Interface. IPv6 ranges are also available to select participants in the Beta program. List of VPC IPs or IP ranges inside the VPC subnet.
This Linode's IPv4 Addresses. Each Linode is assigned a single public IPv4 address upon creation, and may get a single private IPv4 address if needed. You may need to open a support ticket to get additional IPv4 addresses. The IPv4 configuration of the VPC interface.This attribute is only allowed for VPC interfaces.
Information about the Placement Group this Linode is assigned to. NOTE: Placement Groups may not currently be available to all users. Fields related to the Placement Group this instance is assigned to.
A set of IPv4 addresses to be shared with the Instance. These IP addresses can be both private and public, but must be in the same region as the instance. A set of IPv4 addresses to share with this Linode.
Reference to a Stackscript in stackscript to populate stackscriptId.
Policies for referencing.
Selector for a Stackscript in stackscript to populate stackscriptId.
Policies for selection.
A list of tags applied to this object. Tags are case-insensitive and are for organizational purposes only. An array of tags applied to this object. Tags are for organizational purposes only.
THIS IS A BETA FIELD. It is on by default but can be opted out through a Crossplane feature flag. ManagementPolicies specify the array of actions Crossplane is allowed to take on the managed and external resources. This field is planned to replace the DeletionPolicy field in a future release. Currently, both could be set independently and non-default values would be honored if the feature flag is enabled. If both are custom, the DeletionPolicy field will be ignored. See the design doc for more information: https://github.com/crossplane/crossplane/blob/499895a25d1a1a0ba1604944ef98ac7a1a71f197/design/design-doc-observe-only-resources.md?plain=1#L223 and this one: https://github.com/crossplane/crossplane/blob/444267e84783136daa93568b364a5f01228cacbe/design/one-pager-ignore-changes.md
ProviderConfigReference specifies how the provider that will be used to create, observe, update, and delete this managed resource should be configured.
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.
InstanceStatus defines the observed state of Instance.
No description provided.
Configuration options for alert triggers on this Linode.
A list of SSH public keys to deploy for the root user on the newly created Linode. This value can not be imported. Changing A list of SSH public keys to deploy for the root user on the newly created Linode. Only accepted if 'image' is provided.
A list of Linode usernames. If the usernames have associated SSH keys, the keys will be appended to the root user's ~/.ssh/authorized_keys file automatically. This value can not be imported. Changing
A list of Linode usernames. If the usernames have associated SSH keys, the keys will be appended to the root user's ~/.ssh/authorized_keys file automatically. Only accepted if 'image' is provided.
block Configuration profiles define the VM settings and boot behavior of the Linode Instance.
A list of disk or volume attachments for this config. If the boot_config_label omits a devices block, the Linode will not be booted. Device sda-sdh can be either a Disk or Volume identified by disk_label or volume_id. Only one type per slot allowed.
The SDA-SDH slots, represent the Linux block device nodes for the first 8 disks attached to the Linode. Each device must be suplied sequentially. The device can be either a Disk or a Volume identified by disk_label or volume_id. Only one disk identifier is permitted per slot. Devices mapped from sde through sdh are unavailable in "fullvirt" virt_mode. Device can be either a Disk or Volume identified by disk_id or volume_id. Only one type per slot allowed.
(Options) Helpers enabled when booting to this Linode Config. Helpers enabled when booting to this Linode Config.
An array of Network Interfaces for this Linode’s Configuration Profile.
IPv4 CIDR VPC Subnet ranges that are routed to this Interface. IPv6 ranges are also available to select participants in the Beta program. List of VPC IPs or IP ranges inside the VPC subnet.
This Linode's IPv4 Addresses. Each Linode is assigned a single public IPv4 address upon creation, and may get a single private IPv4 address if needed. You may need to open a support ticket to get additional IPv4 addresses. The IPv4 configuration of the VPC interface.This attribute is only allowed for VPC interfaces.
The amount of storage space, in GB. this Linode has access to. A typical Linode will divide this space between a primary disk with an image deployed to it, and a swap disk, usually 512 MB. This is the default configuration created when deploying a Linode with an image through POST /linode/instances.
A list of SSH public keys to deploy for the root user on the newly created Linode. This value can not be imported. Changing A list of SSH public keys to deploy for the root user on the newly created Linode. Only accepted if 'image' is provided.
A list of Linode usernames. If the usernames have associated SSH keys, the keys will be appended to the root user's ~/.ssh/authorized_keys file automatically. This value can not be imported. Changing
A list of Linode usernames. If the usernames have associated SSH keys, the keys will be appended to the root user's ~/.ssh/authorized_keys file automatically. Only accepted if 'image' is provided.
An array of Network Interfaces for this Linode to be created with. If an explicit config or disk is defined, interfaces must be declared in the config block.
IPv4 CIDR VPC Subnet ranges that are routed to this Interface. IPv6 ranges are also available to select participants in the Beta program. List of VPC IPs or IP ranges inside the VPC subnet.
This Linode's IPv4 Addresses. Each Linode is assigned a single public IPv4 address upon creation, and may get a single private IPv4 address if needed. You may need to open a support ticket to get additional IPv4 addresses. The IPv4 configuration of the VPC interface.This attribute is only allowed for VPC interfaces.
This Linode's IPv4 Addresses. Each Linode is assigned a single public IPv4 address upon creation, and may get a single private IPv4 address if needed. You may need to open a support ticket to get additional IPv4 addresses. This Linode's IPv4 Addresses. Each Linode is assigned a single public IPv4 address upon creation, and may get a single private IPv4 address if needed. You may need to open a support ticket to get additional IPv4 addresses.
Information about the Placement Group this Linode is assigned to. NOTE: Placement Groups may not currently be available to all users. Fields related to the Placement Group this instance is assigned to.
A set of IPv4 addresses to be shared with the Instance. These IP addresses can be both private and public, but must be in the same region as the instance. A set of IPv4 addresses to share with this Linode.
A list of tags applied to this object. Tags are case-insensitive and are for organizational purposes only. An array of tags applied to this object. Tags are for organizational purposes only.
Conditions of the resource.
primary
apiVersion: instance.linode.upbound.io/v1alpha1
kind: Instance
metadata:
annotations:
meta.upbound.io/example-id: instance/v1alpha1/sharedips
labels:
testing.upbound.io/example-name: primary
name: primary
spec:
forProvider:
label: node-primary
region: eu-central
type: g6-nanode-1
my-instance
apiVersion: instance.linode.upbound.io/v1alpha1
kind: Instance
metadata:
annotations:
meta.upbound.io/example-id: instance/v1alpha1/disk
labels:
testing.upbound.io/example-name: my-instance
name: my-instance
spec:
forProvider:
label: my-instance
region: us-southeast
type: g6-standard-1
secondary
apiVersion: instance.linode.upbound.io/v1alpha1
kind: Instance
metadata:
annotations:
meta.upbound.io/example-id: instance/v1alpha1/sharedips
labels:
testing.upbound.io/example-name: secondary
name: secondary
spec:
forProvider:
label: node-secondary
region: eu-central
type: g6-nanode-1
foo
apiVersion: instance.linode.upbound.io/v1alpha1
kind: Instance
metadata:
annotations:
meta.upbound.io/example-id: instance/v1alpha1/ip
labels:
testing.upbound.io/example-name: foo
name: foo
spec:
forProvider:
image: linode/ubuntu22.04
label: foobar-test
region: us-east
type: g6-nanode-1
web
apiVersion: instance.linode.upbound.io/v1alpha1
kind: Instance
metadata:
annotations:
meta.upbound.io/example-id: nodebalancer/v1alpha1/node
labels:
testing.upbound.io/example-name: web
name: web
spec:
forProvider:
authorizedKeys:
- ssh-rsa AAAA...Gw== user@example.local
image: linode/ubuntu18.04
label: web-1
privateIp: true
region: us-east
rootPassSecretRef:
key: example-key
name: example-secret
namespace: upbound-system
type: g6-standard-1
my-instance
apiVersion: instance.linode.upbound.io/v1alpha1
kind: Instance
metadata:
annotations:
meta.upbound.io/example-id: instance/v1alpha1/config
labels:
testing.upbound.io/example-name: my-instance
name: my-instance
spec:
forProvider:
label: my-instance
region: us-southeast
type: g6-standard-1
uptest-instance
apiVersion: instance.linode.upbound.io/v1alpha1
kind: Instance
metadata:
name: uptest-instance
spec:
forProvider:
authorizedKeys:
- ssh-rsa foobar.....AAAAA
image: linode/ubuntu22.04
label: provider-linode-test
privateIp: true
region: us-sea
tags:
- rke2
type: g6-standard-2
providerConfigRef:
name: default
web
apiVersion: instance.linode.upbound.io/v1alpha1
kind: Instance
metadata:
annotations:
meta.upbound.io/example-id: instance/v1alpha1/instance
labels:
testing.upbound.io/example-name: web
name: web
spec:
forProvider:
authorizedKeys:
- ssh-rsa AAAA...Gw== user@example.local
group: foo
image: linode/ubuntu18.04
label: simple_instance
privateIp: true
region: us-sea
swapSize: 256
tags:
- foo
type: g6-standard-1
© 2022 Upbound, Inc.
Discover the building blocksfor your internal cloud platform.