ConnectivityTest is the Schema for the ConnectivityTests API. A connectivity test are a static analysis of your resource configurations that enables you to evaluate connectivity to and from Google Cloud resources in your Virtual Private Cloud (VPC) network.
Type
CRD
Group
networkmanagement.gcp.upbound.io
Version
v1beta1
apiVersion: networkmanagement.gcp.upbound.io/v1beta1
kind: ConnectivityTest
ConnectivityTestSpec defines the desired state of ConnectivityTest
No description provided.
Required. Destination specification of the Connectivity Test. You can use a combination of destination IP address, Compute Engine VM instance, or VPC network to uniquely identify the destination location. Even if the destination IP address is not unique, the source IP location is unique. Usually, the analysis can infer the destination endpoint from route information. If the destination you specify is a VM instance and the instance has multiple network interfaces, then you must also specify either a destination IP address or VPC network to identify the destination interface. A reachability analysis proceeds even if the destination location is ambiguous. However, the result can include endpoints that you don't intend to test. Structure is documented below.
Reference to a Instance in compute to populate instance.
Policies for referencing.
Selector for a Instance in compute to populate instance.
Policies for selection.
Reference to a Address in compute to populate ipAddress.
Policies for referencing.
Selector for a Address in compute to populate ipAddress.
Policies for selection.
Reference to a Network in compute to populate network.
Policies for referencing.
Selector for a Network in compute to populate network.
Policies for selection.
Reference to a Address in compute to populate projectId.
Policies for referencing.
Selector for a Address in compute to populate projectId.
Policies for selection.
Other projects that may be relevant for reachability analysis. This is applicable to scenarios where a test can cross project boundaries.
Required. Source specification of the Connectivity Test. You can use a combination of source IP address, virtual machine (VM) instance, or Compute Engine network to uniquely identify the source location. Examples: If the source IP address is an internal IP address within a Google Cloud Virtual Private Cloud (VPC) network, then you must also specify the VPC network. Otherwise, specify the VM instance, which already contains its internal IP address and VPC network information. If the source of the test is within an on-premises network, then you must provide the destination VPC network. If the source endpoint is a Compute Engine VM instance with multiple network interfaces, the instance itself is not sufficient to identify the endpoint. So, you must also specify the source IP address or VPC network. A reachability analysis proceeds even if the source location is ambiguous. However, the test result may include endpoints that you don't intend to test. Structure is documented below.
Reference to a Instance in compute to populate instance.
Policies for referencing.
Selector for a Instance in compute to populate instance.
Policies for selection.
Reference to a Address in compute to populate ipAddress.
Policies for referencing.
Selector for a Address in compute to populate ipAddress.
Policies for selection.
Reference to a Network in compute to populate network.
Policies for referencing.
Selector for a Network in compute to populate network.
Policies for selection.
Reference to a Address in compute to populate projectId.
Policies for referencing.
Selector for a Address in compute to populate projectId.
Policies for selection.
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.
Required. Destination specification of the Connectivity Test. You can use a combination of destination IP address, Compute Engine VM instance, or VPC network to uniquely identify the destination location. Even if the destination IP address is not unique, the source IP location is unique. Usually, the analysis can infer the destination endpoint from route information. If the destination you specify is a VM instance and the instance has multiple network interfaces, then you must also specify either a destination IP address or VPC network to identify the destination interface. A reachability analysis proceeds even if the destination location is ambiguous. However, the result can include endpoints that you don't intend to test. Structure is documented below.
Reference to a Instance in compute to populate instance.
Policies for referencing.
Selector for a Instance in compute to populate instance.
Policies for selection.
Reference to a Address in compute to populate ipAddress.
Policies for referencing.
Selector for a Address in compute to populate ipAddress.
Policies for selection.
Reference to a Network in compute to populate network.
Policies for referencing.
Selector for a Network in compute to populate network.
Policies for selection.
Reference to a Address in compute to populate projectId.
Policies for referencing.
Selector for a Address in compute to populate projectId.
Policies for selection.
Other projects that may be relevant for reachability analysis. This is applicable to scenarios where a test can cross project boundaries.
Required. Source specification of the Connectivity Test. You can use a combination of source IP address, virtual machine (VM) instance, or Compute Engine network to uniquely identify the source location. Examples: If the source IP address is an internal IP address within a Google Cloud Virtual Private Cloud (VPC) network, then you must also specify the VPC network. Otherwise, specify the VM instance, which already contains its internal IP address and VPC network information. If the source of the test is within an on-premises network, then you must provide the destination VPC network. If the source endpoint is a Compute Engine VM instance with multiple network interfaces, the instance itself is not sufficient to identify the endpoint. So, you must also specify the source IP address or VPC network. A reachability analysis proceeds even if the source location is ambiguous. However, the test result may include endpoints that you don't intend to test. Structure is documented below.
Reference to a Instance in compute to populate instance.
Policies for referencing.
Selector for a Instance in compute to populate instance.
Policies for selection.
Reference to a Address in compute to populate ipAddress.
Policies for referencing.
Selector for a Address in compute to populate ipAddress.
Policies for selection.
Reference to a Network in compute to populate network.
Policies for referencing.
Selector for a Network in compute to populate network.
Policies for selection.
Reference to a Address in compute to populate projectId.
Policies for referencing.
Selector for a Address in compute to populate projectId.
Policies for selection.
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.
ConnectivityTestStatus defines the observed state of ConnectivityTest.
No description provided.
Required. Destination specification of the Connectivity Test. You can use a combination of destination IP address, Compute Engine VM instance, or VPC network to uniquely identify the destination location. Even if the destination IP address is not unique, the source IP location is unique. Usually, the analysis can infer the destination endpoint from route information. If the destination you specify is a VM instance and the instance has multiple network interfaces, then you must also specify either a destination IP address or VPC network to identify the destination interface. A reachability analysis proceeds even if the destination location is ambiguous. However, the result can include endpoints that you don't intend to test. Structure is documented below.
Other projects that may be relevant for reachability analysis. This is applicable to scenarios where a test can cross project boundaries.
Required. Source specification of the Connectivity Test. You can use a combination of source IP address, virtual machine (VM) instance, or Compute Engine network to uniquely identify the source location. Examples: If the source IP address is an internal IP address within a Google Cloud Virtual Private Cloud (VPC) network, then you must also specify the VPC network. Otherwise, specify the VM instance, which already contains its internal IP address and VPC network information. If the source of the test is within an on-premises network, then you must provide the destination VPC network. If the source endpoint is a Compute Engine VM instance with multiple network interfaces, the instance itself is not sufficient to identify the endpoint. So, you must also specify the source IP address or VPC network. A reachability analysis proceeds even if the source location is ambiguous. However, the test result may include endpoints that you don't intend to test. Structure is documented below.
Conditions of the resource.
instance-test
apiVersion: networkmanagement.gcp.upbound.io/v1beta1
kind: ConnectivityTest
metadata:
annotations:
meta.upbound.io/example-id: networkmanagement/v1beta1/connectivitytest
labels:
testing.upbound.io/example-name: instance-test
name: instance-test
spec:
forProvider:
destination:
- instanceSelector:
matchLabels:
testing.upbound.io/example-name: destination
name: conn-test-instances
protocol: TCP
source:
- instanceSelector:
matchLabels:
testing.upbound.io/example-name: source
© 2022 Upbound, Inc.
Discover the building blocksfor your internal cloud platform.