BackendGroup is the Schema for the BackendGroups API. An application load balancer distributes the load across cloud resources that are combined into a backend group.
Type
CRD
Group
alb.yandex-cloud.jet.crossplane.io
Version
v1alpha1
apiVersion: alb.yandex-cloud.jet.crossplane.io/v1alpha1
kind: BackendGroup
BackendGroupSpec defines the desired state of BackendGroup
No description provided.
Reference to a Folder in resourcemanager to populate folderId.
Policies for referencing.
Selector for a Folder in resourcemanager to populate folderId.
Policies for selection.
Grpc backend specification that will be used by the ALB Backend Group. Structure is documented below.
Healthcheck specification that will be used by this backend. Structure is documented below.
Grpc Healthcheck specification that will be used by this healthcheck. Structure is documented below.
Load Balancing Config specification that will be used by this backend. Structure is documented below.
References target groups for the backend.
References to TargetGroup to populate targetGroupIds.
Policies for referencing.
Selector for a list of TargetGroup to populate targetGroupIds.
Policies for selection.
Tls specification that will be used by this backend. Structure is documented below.
No description provided.
Http backend specification that will be used by the ALB Backend Group. Structure is documented below.
Healthcheck specification that will be used by this backend. Structure is documented below.
Grpc Healthcheck specification that will be used by this healthcheck. Structure is documented below.
Load Balancing Config specification that will be used by this backend. Structure is documented below.
References target groups for the backend.
References to TargetGroup to populate targetGroupIds.
Policies for referencing.
Selector for a list of TargetGroup to populate targetGroupIds.
Policies for selection.
Tls specification that will be used by this backend. Structure is documented below.
No description provided.
Session affinity mode determines how incoming requests are grouped into one session. Structure is documented below.
Requests received from the same IP are combined into a session. Stream backend groups only support session affinity by client IP address. Structure is documented below. IP address affinity
Requests with the same value of the specified HTTP header, such as with user authentication data, are combined into a session. Allowed only for HTTP and gRPC backend groups. Structure is documented below. Request header affinity
Stream backend specification that will be used by the ALB Backend Group. Structure is documented below.
Healthcheck specification that will be used by this backend. Structure is documented below.
Grpc Healthcheck specification that will be used by this healthcheck. Structure is documented below.
Load Balancing Config specification that will be used by this backend. Structure is documented below.
References target groups for the backend.
References to TargetGroup to populate targetGroupIds.
Policies for referencing.
Selector for a list of TargetGroup to populate targetGroupIds.
Policies for selection.
Tls specification that will be used by this backend. Structure is documented below.
No description provided.
THIS IS A BETA FIELD. It will be honored unless the Management Policies feature flag is disabled. 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.
Reference to a Folder in resourcemanager to populate folderId.
Policies for referencing.
Selector for a Folder in resourcemanager to populate folderId.
Policies for selection.
Grpc backend specification that will be used by the ALB Backend Group. Structure is documented below.
Healthcheck specification that will be used by this backend. Structure is documented below.
Grpc Healthcheck specification that will be used by this healthcheck. Structure is documented below.
Load Balancing Config specification that will be used by this backend. Structure is documented below.
References target groups for the backend.
References to TargetGroup to populate targetGroupIds.
Policies for referencing.
Selector for a list of TargetGroup to populate targetGroupIds.
Policies for selection.
Tls specification that will be used by this backend. Structure is documented below.
No description provided.
Http backend specification that will be used by the ALB Backend Group. Structure is documented below.
Healthcheck specification that will be used by this backend. Structure is documented below.
Grpc Healthcheck specification that will be used by this healthcheck. Structure is documented below.
Load Balancing Config specification that will be used by this backend. Structure is documented below.
References target groups for the backend.
References to TargetGroup to populate targetGroupIds.
Policies for referencing.
Selector for a list of TargetGroup to populate targetGroupIds.
Policies for selection.
Tls specification that will be used by this backend. Structure is documented below.
No description provided.
Session affinity mode determines how incoming requests are grouped into one session. Structure is documented below.
Requests received from the same IP are combined into a session. Stream backend groups only support session affinity by client IP address. Structure is documented below. IP address affinity
Requests with the same value of the specified HTTP header, such as with user authentication data, are combined into a session. Allowed only for HTTP and gRPC backend groups. Structure is documented below. Request header affinity
Stream backend specification that will be used by the ALB Backend Group. Structure is documented below.
Healthcheck specification that will be used by this backend. Structure is documented below.
Grpc Healthcheck specification that will be used by this healthcheck. Structure is documented below.
Load Balancing Config specification that will be used by this backend. Structure is documented below.
References target groups for the backend.
References to TargetGroup to populate targetGroupIds.
Policies for referencing.
Selector for a list of TargetGroup to populate targetGroupIds.
Policies for selection.
Tls specification that will be used by this backend. Structure is documented below.
No description provided.
THIS IS A BETA FIELD. It is on by default but can be opted out through a Crossplane feature flag. 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.
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.
BackendGroupStatus defines the observed state of BackendGroup.
No description provided.
Grpc backend specification that will be used by the ALB Backend Group. Structure is documented below.
Healthcheck specification that will be used by this backend. Structure is documented below.
Grpc Healthcheck specification that will be used by this healthcheck. Structure is documented below.
Load Balancing Config specification that will be used by this backend. Structure is documented below.
References target groups for the backend.
Tls specification that will be used by this backend. Structure is documented below.
No description provided.
Http backend specification that will be used by the ALB Backend Group. Structure is documented below.
Healthcheck specification that will be used by this backend. Structure is documented below.
Grpc Healthcheck specification that will be used by this healthcheck. Structure is documented below.
Load Balancing Config specification that will be used by this backend. Structure is documented below.
References target groups for the backend.
Tls specification that will be used by this backend. Structure is documented below.
No description provided.
Session affinity mode determines how incoming requests are grouped into one session. Structure is documented below.
Requests received from the same IP are combined into a session. Stream backend groups only support session affinity by client IP address. Structure is documented below. IP address affinity
Requests with the same value of the specified HTTP header, such as with user authentication data, are combined into a session. Allowed only for HTTP and gRPC backend groups. Structure is documented below. Request header affinity
Stream backend specification that will be used by the ALB Backend Group. Structure is documented below.
Healthcheck specification that will be used by this backend. Structure is documented below.
Grpc Healthcheck specification that will be used by this healthcheck. Structure is documented below.
Load Balancing Config specification that will be used by this backend. Structure is documented below.
References target groups for the backend.
Tls specification that will be used by this backend. Structure is documented below.
No description provided.
Conditions of the resource.
test-backend-group
apiVersion: alb.yandex-cloud.jet.crossplane.io/v1alpha1
kind: BackendGroup
metadata:
annotations:
meta.upbound.io/example-id: alb/v1alpha1/backendgroup
labels:
testing.upbound.io/example-name: my-bg
name: test-backend-group
spec:
forProvider:
httpBackend:
- healthcheck:
- httpHealthcheck:
- path: /
interval: 1s
timeout: 1s
http2: true
loadBalancingConfig:
- panicThreshold: 50
name: test-http-backend
port: 8080
targetGroupIdsRefs:
- name: test-target-group
tls:
- sni: backend-domain.internal
weight: 1
name: my-backend-group
providerConfigRef:
name: default