RouterNAT is the Schema for the RouterNATs API. A NAT service created in a router.
RouterNATSpec defines the desired state of RouterNAT
No description provided.
A list of URLs of the IP resources to be drained. These IPs must be valid static external IPs that have been assigned to the NAT.
Self-links of NAT IPs. Only valid if natIpAllocateOption is set to MANUAL_ONLY.
A list of rules associated with this NAT. Structure is documented below.
The action to be enforced for traffic that matches this rule. Structure is documented below.
A list of URLs of the IP resources used for this NAT rule. These IP addresses must be valid static external IP addresses assigned to the project. This field is used for public NAT.
A list of URLs of the IP resources to be drained. These IPs must be valid static external IPs that have been assigned to the NAT. These IPs should be used for updating/patching a NAT rule only. This field is used for public NAT.
One or more subnetwork NAT configurations. Only used if source_subnetwork_ip_ranges_to_nat is set to LIST_OF_SUBNETWORKS Structure is documented below.
List of the secondary ranges of the subnetwork that are allowed to use NAT. This can be populated only if LIST_OF_SECONDARY_IP_RANGES is one of the values in sourceIpRangesToNat
List of options for which source IPs in the subnetwork should have NAT enabled. Supported values include: ALL_IP_RANGES, LIST_OF_SECONDARY_IP_RANGES, PRIMARY_IP_RANGE.
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.
apiVersion: compute.gcp.upbound.io/v1beta1 kind: RouterNAT metadata: annotations: meta.upbound.io/example-id: compute/v1beta1/routernat labels: testing.upbound.io/example-name: example_routernat name: example-routernat spec: forProvider: logConfig: - enable: true filter: ERRORS_ONLY natIpAllocateOption: AUTO_ONLY region: us-central1 routerSelector: matchLabels: testing.upbound.io/example-name: example_routernat_router sourceSubnetworkIpRangesToNat: ALL_SUBNETWORKS_ALL_IP_RANGES
Discover the building blocks for your internal cloud platform.
© 2022 Upbound, Inc.
© 2022 Upbound, Inc.
Discover the building blocksfor your internal cloud platform.