Subnet is the Schema for the Subnets API. A VPC network is a virtual version of the traditional physical networks that exist within and between physical data centers.
Type
CRD
Group
vpc.yandex-cloud.jet.crossplane.io
Version
v1alpha1
apiVersion: vpc.yandex-cloud.jet.crossplane.io/v1alpha1
kind: Subnet
SubnetSpec defines the desired state of Subnet
No description provided.
Options for DHCP client. The structure is documented below.
Domain name server IP addresses.
NTP server IP addresses.
Reference to a Folder in resourcemanager to populate folderId.
Policies for referencing.
Selector for a Folder in resourcemanager to populate folderId.
Policies for selection.
Reference to a Network to populate networkId.
Policies for referencing.
Selector for a Network to populate networkId.
Policies for selection.
A list of blocks of internal IPv4 addresses that are owned by this subnet. Provide this property when you create the subnet. For example, 10.0.0.0/22 or 192.168.0.0/16. Blocks of addresses must be unique and non-overlapping within a network. Minimum subnet size is /28, and maximum subnet size is /16. Only IPv4 is supported.
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.
Options for DHCP client. The structure is documented below.
Domain name server IP addresses.
NTP server IP addresses.
Reference to a Folder in resourcemanager to populate folderId.
Policies for referencing.
Selector for a Folder in resourcemanager to populate folderId.
Policies for selection.
Reference to a Network to populate networkId.
Policies for referencing.
Selector for a Network to populate networkId.
Policies for selection.
A list of blocks of internal IPv4 addresses that are owned by this subnet. Provide this property when you create the subnet. For example, 10.0.0.0/22 or 192.168.0.0/16. Blocks of addresses must be unique and non-overlapping within a network. Minimum subnet size is /28, and maximum subnet size is /16. Only IPv4 is supported.
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.
SubnetStatus defines the observed state of Subnet.
No description provided.
Options for DHCP client. The structure is documented below.
Domain name server IP addresses.
NTP server IP addresses.
A list of blocks of internal IPv4 addresses that are owned by this subnet. Provide this property when you create the subnet. For example, 10.0.0.0/22 or 192.168.0.0/16. Blocks of addresses must be unique and non-overlapping within a network. Minimum subnet size is /28, and maximum subnet size is /16. Only IPv4 is supported.
An optional list of blocks of IPv6 addresses that are owned by this subnet.
Conditions of the resource.
example-subnet-a
apiVersion: vpc.yandex-cloud.jet.crossplane.io/v1alpha1
kind: Subnet
metadata:
name: example-subnet-a
spec:
forProvider:
name: example-subnet-a
networkIdRef:
name: example-net
v4CidrBlocks:
- 10.0.0.0/24
zone: ru-central1-a
providerConfigRef:
name: default