Subnetwork is the Schema for the Subnetworks API. A VPC network is a virtual version of the traditional physical networks that exist within and between physical data centers.
Type
CRD
Group
compute.gcp.upbound.io
Version
apiVersion: compute.gcp.upbound.io/v1beta1
kind: Subnetwork
SubnetworkSpec defines the desired state of Subnetwork
No description provided.
This field denotes the VPC flow logging options for this subnetwork. If logging is enabled, logs are exported to Cloud Logging. Flow logging isn't supported if the subnet purpose field is set to subnetwork is REGIONAL_MANAGED_PROXY or GLOBAL_MANAGED_PROXY. Structure is documented below.
List of metadata fields that should be added to reported logs. Can only be specified if VPC flow logs for this subnetwork is enabled and "metadata" is set to CUSTOM_METADATA.
Reference to a Network in compute to populate network.
Policies for referencing.
Selector for a Network in compute to populate network.
Policies for selection.
An array of configurations for secondary IP ranges for VM instances contained in this subnetwork. The primary IP of such VM must belong to the primary ipCidrRange of the subnetwork. The alias IPs may belong to either primary or secondary ranges. Note: This field uses attr-as-block mode to avoid breaking users during the 0.12 upgrade. To explicitly send a list of zero objects you must use the following syntax: example=[] For more details about this behavior, see this section. Structure is documented 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.
This field denotes the VPC flow logging options for this subnetwork. If logging is enabled, logs are exported to Cloud Logging. Flow logging isn't supported if the subnet purpose field is set to subnetwork is REGIONAL_MANAGED_PROXY or GLOBAL_MANAGED_PROXY. Structure is documented below.
List of metadata fields that should be added to reported logs. Can only be specified if VPC flow logs for this subnetwork is enabled and "metadata" is set to CUSTOM_METADATA.
Reference to a Network in compute to populate network.
Policies for referencing.
Selector for a Network in compute to populate network.
Policies for selection.
An array of configurations for secondary IP ranges for VM instances contained in this subnetwork. The primary IP of such VM must belong to the primary ipCidrRange of the subnetwork. The alias IPs may belong to either primary or secondary ranges. Note: This field uses attr-as-block mode to avoid breaking users during the 0.12 upgrade. To explicitly send a list of zero objects you must use the following syntax: example=[] For more details about this behavior, see this section. Structure is documented 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.
SubnetworkStatus defines the observed state of Subnetwork.
No description provided.
This field denotes the VPC flow logging options for this subnetwork. If logging is enabled, logs are exported to Cloud Logging. Flow logging isn't supported if the subnet purpose field is set to subnetwork is REGIONAL_MANAGED_PROXY or GLOBAL_MANAGED_PROXY. Structure is documented below.
List of metadata fields that should be added to reported logs. Can only be specified if VPC flow logs for this subnetwork is enabled and "metadata" is set to CUSTOM_METADATA.
An array of configurations for secondary IP ranges for VM instances contained in this subnetwork. The primary IP of such VM must belong to the primary ipCidrRange of the subnetwork. The alias IPs may belong to either primary or secondary ranges. Note: This field uses attr-as-block mode to avoid breaking users during the 0.12 upgrade. To explicitly send a list of zero objects you must use the following syntax: example=[] For more details about this behavior, see this section. Structure is documented below.
Conditions of the resource.
network-endpoint-group
apiVersion: compute.gcp.upbound.io/v1beta1
kind: Subnetwork
metadata:
annotations:
meta.upbound.io/example-id: compute/v1beta1/networkendpointgroup
labels:
testing.upbound.io/example-name: network-endpoint-group
name: network-endpoint-group
spec:
forProvider:
ipCidrRange: 10.2.0.0/16
networkSelector:
matchLabels:
testing.upbound.io/example-name: network-endpoint-group
region: us-central1
secondaryIpRange:
- ipCidrRange: 192.168.10.0/24
rangeName: test-secondary-range-update1
network-endpoint
apiVersion: compute.gcp.upbound.io/v1beta1
kind: Subnetwork
metadata:
annotations:
meta.upbound.io/example-id: compute/v1beta1/networkendpoint
labels:
testing.upbound.io/example-name: network-endpoint
name: network-endpoint
spec:
forProvider:
ipCidrRange: 10.2.0.0/16
networkSelector:
matchLabels:
testing.upbound.io/example-name: network-endpoint
region: us-central1
example-subnet
apiVersion: compute.gcp.upbound.io/v1beta1
kind: Subnetwork
metadata:
annotations:
meta.upbound.io/example-id: compute/v1beta1/subnetwork
labels:
testing.upbound.io/example-name: example_subnet
name: example-subnet
spec:
forProvider:
ipCidrRange: 10.2.0.0/16
networkSelector:
matchLabels:
testing.upbound.io/example-name: example_subnet_network
region: us-central1
secondaryIpRange:
- ipCidrRange: 192.168.10.0/24
rangeName: test-secondary-range-update1
service-attachment
apiVersion: compute.gcp.upbound.io/v1beta1
kind: Subnetwork
metadata:
annotations:
meta.upbound.io/example-id: compute/v1beta1/serviceattachment
upjet.upbound.io/manual-intervention: Must be authorized to administer the domain gcp.example.com
labels:
testing.upbound.io/example-name: service-attachment
name: service-attachment
spec:
forProvider:
ipCidrRange: 10.0.0.0/16
networkSelector:
matchLabels:
testing.upbound.io/example-name: service-attachment
region: us-central1
packet-mirroring
apiVersion: compute.gcp.upbound.io/v1beta1
kind: Subnetwork
metadata:
annotations:
meta.upbound.io/example-id: compute/v1beta1/packetmirroring
labels:
testing.upbound.io/example-name: packet-mirroring
name: packet-mirroring
spec:
forProvider:
ipCidrRange: 10.2.0.0/16
networkSelector:
matchLabels:
testing.upbound.io/example-name: packet-mirroring
region: us-central1
instance-group-named-port
apiVersion: compute.gcp.upbound.io/v1beta1
kind: Subnetwork
metadata:
annotations:
meta.upbound.io/example-id: compute/v1beta1/instancegroupnamedport
upjet.upbound.io/manual-intervention: Instance group name is generated
(gke-instance-group-named-default-pool-eb15fe12-grp). Needs explicit
reference
labels:
testing.upbound.io/example-name: instance-group-named-port
name: instance-group-named-port
spec:
forProvider:
ipCidrRange: 10.0.36.0/24
networkSelector:
matchLabels:
testing.upbound.io/example-name: instance-group-named-port
region: us-central1
forwarding-rule-proxy
apiVersion: compute.gcp.upbound.io/v1beta1
kind: Subnetwork
metadata:
annotations:
meta.upbound.io/example-id: compute/v1beta1/forwardingrule
labels:
testing.upbound.io/example-name: forwarding-rule-proxy
name: forwarding-rule-proxy
spec:
forProvider:
ipCidrRange: 10.0.0.0/24
networkSelector:
matchLabels:
testing.upbound.io/example-name: forwarding-rule
purpose: INTERNAL_HTTPS_LOAD_BALANCER
region: us-central1
role: ACTIVE
example-routernat-subnetwork
apiVersion: compute.gcp.upbound.io/v1beta1
kind: Subnetwork
metadata:
annotations:
meta.upbound.io/example-id: compute/v1beta1/routernat
labels:
testing.upbound.io/example-name: example_routernat_network
name: example-routernat-subnetwork
spec:
forProvider:
ipCidrRange: 10.0.0.0/16
networkSelector:
matchLabels:
testing.upbound.io/example-name: example_routernat_network
region: us-central1
external-vpn-gateway-1
apiVersion: compute.gcp.upbound.io/v1beta1
kind: Subnetwork
metadata:
annotations:
meta.upbound.io/example-id: compute/v1beta1/externalvpngateway
labels:
testing.upbound.io/example-name: external-vpn-gateway-1
name: external-vpn-gateway-1
spec:
forProvider:
ipCidrRange: 10.0.1.0/24
networkSelector:
matchLabels:
testing.upbound.io/example-name: external-vpn-gateway
region: us-central1
forwarding-rule-ilb
apiVersion: compute.gcp.upbound.io/v1beta1
kind: Subnetwork
metadata:
annotations:
meta.upbound.io/example-id: compute/v1beta1/forwardingrule
labels:
testing.upbound.io/example-name: forwarding-rule-ilb
name: forwarding-rule-ilb
spec:
forProvider:
ipCidrRange: 10.0.1.0/24
networkSelector:
matchLabels:
testing.upbound.io/example-name: forwarding-rule
region: us-central1
example-instance-subnetwork
apiVersion: compute.gcp.upbound.io/v1beta1
kind: Subnetwork
metadata:
annotations:
meta.upbound.io/example-id: compute/v1beta1/instance
labels:
testing.upbound.io/example-name: example_instance_network
name: example-instance-subnetwork
spec:
forProvider:
ipCidrRange: 10.0.0.0/16
networkSelector:
matchLabels:
testing.upbound.io/example-name: example_instance_network
region: us-central1
example-ip-address-subnet
apiVersion: compute.gcp.upbound.io/v1beta1
kind: Subnetwork
metadata:
annotations:
meta.upbound.io/example-id: compute/v1beta1/address
labels:
testing.upbound.io/example-name: example_ip_address_subnet
name: example-ip-address-subnet
spec:
forProvider:
ipCidrRange: 10.0.0.0/16
networkSelector:
matchLabels:
testing.upbound.io/example-name: example_ip_address_network
region: us-central1
subnetwork-iam-member
apiVersion: compute.gcp.upbound.io/v1beta1
kind: Subnetwork
metadata:
annotations:
meta.upbound.io/example-id: compute/v1beta1/subnetworkiammember
labels:
testing.upbound.io/example-name: subnetwork-iam-member
name: subnetwork-iam-member
spec:
forProvider:
ipCidrRange: 10.2.0.0/16
networkSelector:
matchLabels:
testing.upbound.io/example-name: subnetwork-iam-member
region: us-central1
external-vpn-gateway-2
apiVersion: compute.gcp.upbound.io/v1beta1
kind: Subnetwork
metadata:
annotations:
meta.upbound.io/example-id: compute/v1beta1/externalvpngateway
labels:
testing.upbound.io/example-name: external-vpn-gateway-2
name: external-vpn-gateway-2
spec:
forProvider:
ipCidrRange: 10.0.2.0/24
networkSelector:
matchLabels:
testing.upbound.io/example-name: external-vpn-gateway
region: us-west1
route
apiVersion: compute.gcp.upbound.io/v1beta1
kind: Subnetwork
metadata:
annotations:
meta.upbound.io/example-id: compute/v1beta1/route
labels:
testing.upbound.io/example-name: route
name: route
spec:
forProvider:
ipCidrRange: 10.132.1.0/24
networkSelector:
matchLabels:
testing.upbound.io/example-name: route
region: us-central1
global-forwarding-rule
apiVersion: compute.gcp.upbound.io/v1beta1
kind: Subnetwork
metadata:
annotations:
meta.upbound.io/example-id: compute/v1beta1/globalforwardingrule
labels:
testing.upbound.io/example-name: global-forwarding-rule
name: global-forwarding-rule
spec:
forProvider:
ipCidrRange: 10.0.1.0/24
networkSelector:
matchLabels:
testing.upbound.io/example-name: global-forwarding-rule
region: us-central1
service-attachment
apiVersion: compute.gcp.upbound.io/v1beta1
kind: Subnetwork
metadata:
annotations:
meta.upbound.io/example-id: compute/v1beta1/serviceattachment
upjet.upbound.io/manual-intervention: Must be authorized to administer the domain gcp.example.com
labels:
testing.upbound.io/example-name: service-attachment
name: service-attachment
spec:
forProvider:
ipCidrRange: 10.1.0.0/16
networkSelector:
matchLabels:
testing.upbound.io/example-name: service-attachment
purpose: PRIVATE_SERVICE_CONNECT
region: us-central1