ForwardingRule is the Schema for the ForwardingRules API. A ForwardingRule resource.
Type
CRD
Group
compute.gcp.upbound.io
Version
v1beta1
apiVersion: compute.gcp.upbound.io/v1beta1
kind: ForwardingRule
ForwardingRuleSpec defines the desired state of ForwardingRule
No description provided.
Reference to a RegionBackendService to populate backendService.
Policies for referencing.
Selector for a RegionBackendService 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.
This field is used along with internal load balancing and network load balancer when the forwarding rule references a backend service and when protocol is not L3_DEFAULT. A single port or a comma separated list of ports can be configured. Only packets addressed to these ports will be forwarded to the backends configured with this forwarding rule. You can only use one of ports and portRange, or allPorts. The three are mutually exclusive. You may specify a maximum of up to 5 ports, which can be non-contiguous.
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.
ProviderConfigReference specifies how the provider that will be used to create, observe, update, and delete this managed resource should be configured.
Policies for referencing.
ProviderReference specifies the provider that will be used to create, observe, update, and delete this managed resource. Deprecated: Please use ProviderConfigReference, i.e. providerConfigRef
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.
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
© 2022 Upbound, Inc.
Discover the building blocksfor your internal cloud platform.