InstanceV2 is the Schema for the InstanceV2s API. Manages a V2 VM instance resource within OpenStack.
Type
CRD
Group
compute.openstack.crossplane.io
Version
v1alpha1
apiVersion: compute.openstack.crossplane.io/v1alpha1
kind: InstanceV2
InstanceV2Spec defines the desired state of InstanceV2
No description provided.
Configuration of block devices. The block_device structure is documented below. Changing this creates a new server. You can specify multiple block devices which will create an instance with multiple disks. This configuration is very flexible, so please see the following reference for more information.
Reference to a KeypairV2 to populate keyPair.
Policies for referencing.
Selector for a KeypairV2 to populate keyPair.
Policies for selection.
An array of one or more networks to attach to the instance. The network object structure is documented below. Changing this creates a new server.
Provide the Nova scheduler with hints on how the instance should be launched. The available hints are described below.
The names of cells where not to build the instance.
A list of instance UUIDs. The instance will be scheduled on a different host than all other instances.
A conditional query that a compute node must pass in order to host an instance. The query must use the JsonFilter syntax which is described here. At this time, only simple queries are supported. Compound queries using and, or, or not are not supported. An example of a simple query is:
A list of instance UUIDs. The instance will be scheduled on the same host of those specified.
An array of one or more security group names to associate with the server. Changing this results in adding/removing security groups from the existing server. Note: When attaching the instance to networks using Ports, place the security groups on the Port and not the instance. Note: Names should be used and not ids, as ids trigger unnecessary updates.
References to SecgroupV2 to populate securityGroups.
Policies for referencing.
Selector for a list of SecgroupV2 to populate securityGroups.
Policies for selection.
A set of string tags for the instance. Changing this updates the existing instance tags.
Map of additional vendor-specific options. Supported options are described below.
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 of block devices. The block_device structure is documented below. Changing this creates a new server. You can specify multiple block devices which will create an instance with multiple disks. This configuration is very flexible, so please see the following reference for more information.
An array of one or more networks to attach to the instance. The network object structure is documented below. Changing this creates a new server.
Provide the Nova scheduler with hints on how the instance should be launched. The available hints are described below.
The names of cells where not to build the instance.
A list of instance UUIDs. The instance will be scheduled on a different host than all other instances.
A conditional query that a compute node must pass in order to host an instance. The query must use the JsonFilter syntax which is described here. At this time, only simple queries are supported. Compound queries using and, or, or not are not supported. An example of a simple query is:
A list of instance UUIDs. The instance will be scheduled on the same host of those specified.
A set of string tags for the instance. Changing this updates the existing instance tags.
Map of additional vendor-specific options. Supported options are described below.
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.
InstanceV2Status defines the observed state of InstanceV2.
No description provided.
The collection of tags assigned on the instance, which have been explicitly and implicitly added.
Configuration of block devices. The block_device structure is documented below. Changing this creates a new server. You can specify multiple block devices which will create an instance with multiple disks. This configuration is very flexible, so please see the following reference for more information.
An array of one or more networks to attach to the instance. The network object structure is documented below. Changing this creates a new server.
Provide the Nova scheduler with hints on how the instance should be launched. The available hints are described below.
The names of cells where not to build the instance.
A list of instance UUIDs. The instance will be scheduled on a different host than all other instances.
A conditional query that a compute node must pass in order to host an instance. The query must use the JsonFilter syntax which is described here. At this time, only simple queries are supported. Compound queries using and, or, or not are not supported. An example of a simple query is:
A list of instance UUIDs. The instance will be scheduled on the same host of those specified.
An array of one or more security group names to associate with the server. Changing this results in adding/removing security groups from the existing server. Note: When attaching the instance to networks using Ports, place the security groups on the Port and not the instance. Note: Names should be used and not ids, as ids trigger unnecessary updates.
A set of string tags for the instance. Changing this updates the existing instance tags.
Map of additional vendor-specific options. Supported options are described below.
Conditions of the resource.
© 2022 Upbound, Inc.
Discover the building blocksfor your internal cloud platform.