RouterPeer is the Schema for the RouterPeers API. BGP information that must be configured into the routing stack to establish BGP peering.
Type
CRD
Group
compute.gcp.upbound.io
Version
v1beta1
apiVersion: compute.gcp.upbound.io/v1beta1
kind: RouterPeer
RouterPeerSpec defines the desired state of RouterPeer
No description provided.
User-specified list of prefix groups to advertise in custom mode, which can take one of the following options:
User-specified list of individual IP ranges to advertise in custom mode. This field can only be populated if advertiseMode is CUSTOM and is advertised to all peers of the router. These IP ranges will be advertised in addition to any specified groups. Leave this field blank to advertise no custom IP ranges. Structure is documented below.
BFD configuration for the BGP peering. Structure is documented below.
Reference to a RouterInterface in compute to populate interface.
Policies for referencing.
Selector for a RouterInterface in compute to populate interface.
Policies for selection.
Reference to a Address in compute to populate peerIpAddress.
Policies for referencing.
Selector for a Address in compute to populate peerIpAddress.
Policies for selection.
Reference to a Router in compute to populate region.
Policies for referencing.
Selector for a Router in compute to populate region.
Policies for selection.
Reference to a Instance in compute to populate routerApplianceInstance.
Policies for referencing.
Selector for a Instance in compute to populate routerApplianceInstance.
Policies for selection.
Reference to a Router in compute to populate router.
Policies for referencing.
Selector for a Router in compute to populate router.
Policies for selection.
THIS IS AN ALPHA FIELD. Do not use it in production. It is not honored unless the relevant Crossplane feature flag is enabled, and may be changed or removed without notice. 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.
User-specified list of prefix groups to advertise in custom mode, which can take one of the following options:
User-specified list of individual IP ranges to advertise in custom mode. This field can only be populated if advertiseMode is CUSTOM and is advertised to all peers of the router. These IP ranges will be advertised in addition to any specified groups. Leave this field blank to advertise no custom IP ranges. Structure is documented below.
BFD configuration for the BGP peering. Structure is documented below.
THIS IS AN ALPHA FIELD. Do not use it in production. It is not honored unless the relevant Crossplane feature flag is enabled, and may be changed or removed without notice. 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.
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.
RouterPeerStatus defines the observed state of RouterPeer.
No description provided.
User-specified list of prefix groups to advertise in custom mode, which can take one of the following options:
User-specified list of individual IP ranges to advertise in custom mode. This field can only be populated if advertiseMode is CUSTOM and is advertised to all peers of the router. These IP ranges will be advertised in addition to any specified groups. Leave this field blank to advertise no custom IP ranges. Structure is documented below.
BFD configuration for the BGP peering. Structure is documented below.
Conditions of the resource.
router-peer
apiVersion: compute.gcp.upbound.io/v1beta1
kind: RouterPeer
metadata:
annotations:
meta.upbound.io/example-id: compute/v1beta1/routerpeer
labels:
testing.upbound.io/example-name: router_peer
name: router-peer
spec:
forProvider:
advertisedRoutePriority: 100
interfaceSelector:
matchLabels:
testing.upbound.io/example-name: router_peer
peerAsn: 65513
peerIpAddress: 169.254.1.2
regionSelector:
matchLabels:
testing.upbound.io/example-name: router_peer
routerSelector:
matchLabels:
testing.upbound.io/example-name: router_peer