TrafficManagerNestedEndpoint is the Schema for the TrafficManagerNestedEndpoints API. Manages a Nested Endpoint within a Traffic Manager Profile.
TrafficManagerNestedEndpointSpec defines the desired state of TrafficManagerNestedEndpoint
No description provided.
A list of Geographic Regions used to distribute traffic, such as WORLD, UK or DE. The same location can't be specified in two endpoints. See the Geographic Hierarchies documentation for more information.
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.
TrafficManagerNestedEndpointStatus defines the observed state of TrafficManagerNestedEndpoint.
apiVersion: network.azure.upbound.io/v1beta1 kind: TrafficManagerNestedEndpoint metadata: annotations: meta.upbound.io/example-id: network/v1beta1/trafficmanagernestedendpoint labels: testing.upbound.io/example-name: example name: nestedendpoint spec: forProvider: minimumChildEndpoints: 9 priority: 1 profileIdSelector: matchLabels: testing.upbound.io/example-name: parent targetResourceIdSelector: matchLabels: testing.upbound.io/example-name: nested weight: 5
Discover the building blocks for your internal cloud platform.
© 2022 Upbound, Inc.
© 2022 Upbound, Inc.
Discover the building blocksfor your internal cloud platform.