NetworkPeering is the Schema for the NetworkPeerings API. Manages a network peering within GCE.
Type
CRD
Group
compute.gcp.upbound.io
Version
v1beta1
apiVersion: compute.gcp.upbound.io/v1beta1
kind: NetworkPeering
NetworkPeeringSpec defines the desired state of NetworkPeering
No description provided.
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 Network in compute to populate peerNetwork.
Policies for referencing.
Selector for a Network in compute to populate peerNetwork.
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.
NetworkPeeringStatus defines the observed state of NetworkPeering.
No description provided.
Conditions of the resource.
peering-primary-routes-secondary
apiVersion: compute.gcp.upbound.io/v1beta1
kind: NetworkPeering
metadata:
annotations:
meta.upbound.io/example-id: compute/v1beta1/networkpeeringroutesconfig
labels:
testing.upbound.io/example-name: peering-primary-routes-secondary
name: peering-primary-routes-secondary
spec:
forProvider:
networkSelector:
matchLabels:
testing.upbound.io/example-name: peering-primary-routes-secondary
peerNetworkSelector:
matchLabels:
testing.upbound.io/example-name: peering-primary-routes-primary
peering-primary-routes-primary
apiVersion: compute.gcp.upbound.io/v1beta1
kind: NetworkPeering
metadata:
annotations:
meta.upbound.io/example-id: compute/v1beta1/networkpeeringroutesconfig
labels:
testing.upbound.io/example-name: peering-primary-routes-primary
name: peering-primary-routes-primary
spec:
forProvider:
exportCustomRoutes: true
importCustomRoutes: true
networkSelector:
matchLabels:
testing.upbound.io/example-name: peering-primary-routes-primary
peerNetworkSelector:
matchLabels:
testing.upbound.io/example-name: peering-primary-routes-secondary
network-peering
apiVersion: compute.gcp.upbound.io/v1beta1
kind: NetworkPeering
metadata:
annotations:
meta.upbound.io/example-id: compute/v1beta1/networkpeering
labels:
testing.upbound.io/example-name: network-peering
name: network-peering
spec:
forProvider:
networkSelector:
matchLabels:
testing.upbound.io/example-name: network-peering-1
peerNetworkSelector:
matchLabels:
testing.upbound.io/example-name: network-peering-2
© 2022 Upbound, Inc.
Discover the building blocksfor your internal cloud platform.