ExpressRouteCircuitPeering is the Schema for the ExpressRouteCircuitPeerings API. Manages an ExpressRoute Circuit Peering.
Type
CRD
Group
network.azure.upbound.io
Version
v1beta1
apiVersion: network.azure.upbound.io/v1beta1
kind: ExpressRouteCircuitPeering
ExpressRouteCircuitPeeringSpec defines the desired state of ExpressRouteCircuitPeering
No description provided.
Reference to a ExpressRouteCircuit to populate expressRouteCircuitName.
Policies for referencing.
Selector for a ExpressRouteCircuit to populate expressRouteCircuitName.
Policies for selection.
A ipv6 block as defined below.
A microsoft_peering block as defined below.
A microsoft_peering_config block as defined below. Required when peering_type is set to MicrosoftPeering and config for IPv4.
A list of Advertised Public Prefixes.
Reference to a ResourceGroup in azure to populate resourceGroupName.
Policies for referencing.
Selector for a ResourceGroup in azure to populate resourceGroupName.
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.
ExpressRouteCircuitPeeringStatus defines the observed state of ExpressRouteCircuitPeering.
No description provided.
Conditions of the resource.
example
apiVersion: network.azure.upbound.io/v1beta1
kind: ExpressRouteCircuitPeering
metadata:
annotations:
crossplane.io/external-name: MicrosoftPeering
meta.upbound.io/example-id: network/v1beta1/expressroutecircuitpeering
labels:
testing.upbound.io/example-name: example
name: example
spec:
forProvider:
expressRouteCircuitNameSelector:
matchLabels:
testing.upbound.io/example-name: example
ipv6:
- microsoftPeering:
- advertisedPublicPrefixes:
- 2002:db01::/126
primaryPeerAddressPrefix: 2002:db01::/126
secondaryPeerAddressPrefix: 2003:db01::/126
microsoftPeeringConfig:
- advertisedPublicPrefixes:
- 123.1.0.0/24
peerAsn: 100
primaryPeerAddressPrefix: 123.0.0.0/30
resourceGroupNameSelector:
matchLabels:
testing.upbound.io/example-name: example
secondaryPeerAddressPrefix: 123.0.0.4/30
vlanId: 300
example
apiVersion: network.azure.upbound.io/v1beta1
kind: ExpressRouteCircuitPeering
metadata:
annotations:
crossplane.io/external-name: MicrosoftPeering
name: example
spec:
forProvider:
expressRouteCircuitNameRef:
name: example-circuit
ipv6:
- microsoftPeering:
- advertisedPublicPrefixes:
- 2002:db01::/126
primaryPeerAddressPrefix: 2002:db01::/126
secondaryPeerAddressPrefix: 2003:db01::/126
microsoftPeeringConfig:
- advertisedPublicPrefixes:
- 123.2.0.0/24
peerAsn: 100
primaryPeerAddressPrefix: 123.0.0.0/30
resourceGroupNameRef:
name: example-expressroute-rg
secondaryPeerAddressPrefix: 123.0.0.4/30
vlanId: 300
© 2022 Upbound, Inc.
Discover the building blocksfor your internal cloud platform.