ForwardingRule is the Schema for the ForwardingRules API. A ForwardingRule resource.
Type
CRD
Group
compute.gcp.upbound.io
Version
apiVersion: compute.gcp.upbound.io/v1beta1
kind: ForwardingRule
ForwardingRuleSpec defines the desired state of ForwardingRule
No description provided.
Reference to a RegionBackendService in compute to populate backendService.
Policies for referencing.
Selector for a RegionBackendService in compute to populate backendService.
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.
The ports, portRange, and allPorts fields are mutually exclusive. Only packets addressed to ports in the specified range will be forwarded to the backends configured with this forwarding rule. The ports field has the following limitations:
If not empty, this Forwarding Rule will only forward the traffic when the source IP address matches one of the IP addresses or CIDR ranges set here. Note that a Forwarding Rule can only have up to 64 source IP ranges, and this field can only be used with a regional Forwarding Rule whose scheme is EXTERNAL. Each sourceIpRange entry should be either an IP address (for example, 1.2.3.4) or a CIDR range (for example, 1.2.3.0/24).
Reference to a Subnetwork in compute to populate subnetwork.
Policies for referencing.
Selector for a Subnetwork in compute to populate subnetwork.
Policies for selection.
Reference to a RegionTargetHTTPProxy in compute to populate target.
Policies for referencing.
Selector for a RegionTargetHTTPProxy in compute to populate target.
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.
Reference to a RegionBackendService in compute to populate backendService.
Policies for referencing.
Selector for a RegionBackendService in compute to populate backendService.
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.
The ports, portRange, and allPorts fields are mutually exclusive. Only packets addressed to ports in the specified range will be forwarded to the backends configured with this forwarding rule. The ports field has the following limitations:
If not empty, this Forwarding Rule will only forward the traffic when the source IP address matches one of the IP addresses or CIDR ranges set here. Note that a Forwarding Rule can only have up to 64 source IP ranges, and this field can only be used with a regional Forwarding Rule whose scheme is EXTERNAL. Each sourceIpRange entry should be either an IP address (for example, 1.2.3.4) or a CIDR range (for example, 1.2.3.0/24).
Reference to a Subnetwork in compute to populate subnetwork.
Policies for referencing.
Selector for a Subnetwork in compute to populate subnetwork.
Policies for selection.
Reference to a RegionTargetHTTPProxy in compute to populate target.
Policies for referencing.
Selector for a RegionTargetHTTPProxy in compute to populate target.
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.
ForwardingRuleStatus defines the observed state of ForwardingRule.
No description provided.
The ports, portRange, and allPorts fields are mutually exclusive. Only packets addressed to ports in the specified range will be forwarded to the backends configured with this forwarding rule. The ports field has the following limitations:
If not empty, this Forwarding Rule will only forward the traffic when the source IP address matches one of the IP addresses or CIDR ranges set here. Note that a Forwarding Rule can only have up to 64 source IP ranges, and this field can only be used with a regional Forwarding Rule whose scheme is EXTERNAL. Each sourceIpRange entry should be either an IP address (for example, 1.2.3.4) or a CIDR range (for example, 1.2.3.0/24).
Conditions of the resource.
service-attachment
apiVersion: compute.gcp.upbound.io/v1beta1
kind: ForwardingRule
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:
ipAddressSelector:
matchLabels:
testing.upbound.io/example-name: service-attachment
loadBalancingScheme: ""
networkSelector:
matchLabels:
testing.upbound.io/example-name: service-attachment
region: us-central1
targetSelector:
matchLabels:
testing.upbound.io/example-name: service-attachment
vpn-tunnel-esp
apiVersion: compute.gcp.upbound.io/v1beta1
kind: ForwardingRule
metadata:
annotations:
meta.upbound.io/example-id: compute/v1beta1/vpntunnel
upjet.upbound.io/manual-intervention: Dependant reference types not currently supported
labels:
testing.upbound.io/example-name: vpn-tunnel-esp
name: vpn-tunnel-esp
spec:
forProvider:
ipAddressSelector:
matchLabels:
testing.upbound.io/example-name: vpn-tunnel
ipProtocol: ESP
region: us-central1
targetSelector:
matchLabels:
testing.upbound.io/example-name: vpn-tunnel
service-attachment
apiVersion: compute.gcp.upbound.io/v1beta1
kind: ForwardingRule
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:
allPorts: true
backendServiceSelector:
matchLabels:
testing.upbound.io/example-name: service-attachment
loadBalancingScheme: INTERNAL
networkSelector:
matchLabels:
testing.upbound.io/example-name: service-attachment
region: us-central1
subnetworkSelector:
matchLabels:
testing.upbound.io/example-name: service-attachment
packet-mirroring
apiVersion: compute.gcp.upbound.io/v1beta1
kind: ForwardingRule
metadata:
annotations:
meta.upbound.io/example-id: compute/v1beta1/packetmirroring
labels:
testing.upbound.io/example-name: packet-mirroring
name: packet-mirroring
spec:
forProvider:
allPorts: true
backendServiceSelector:
matchLabels:
testing.upbound.io/example-name: packet-mirroring
ipProtocol: TCP
isMirroringCollector: true
loadBalancingScheme: INTERNAL
networkSelector:
matchLabels:
testing.upbound.io/example-name: packet-mirroring
networkTier: PREMIUM
region: us-central1
subnetworkSelector:
matchLabels:
testing.upbound.io/example-name: packet-mirroring
forwarding-rule
apiVersion: compute.gcp.upbound.io/v1beta1
kind: ForwardingRule
metadata:
annotations:
meta.upbound.io/example-id: compute/v1beta1/forwardingrule
labels:
testing.upbound.io/example-name: forwarding-rule
name: forwarding-rule
spec:
forProvider:
ipProtocol: TCP
loadBalancingScheme: INTERNAL_MANAGED
networkSelector:
matchLabels:
testing.upbound.io/example-name: forwarding-rule
networkTier: PREMIUM
portRange: "80"
region: us-central1
subnetworkSelector:
matchLabels:
testing.upbound.io/example-name: forwarding-rule-ilb
targetSelector:
matchLabels:
testing.upbound.io/example-name: forwarding-rule