LoadBalancer is the Schema for the LoadBalancers API. A Load Balancer is used for receiving incoming traffic and transmitting it to the backend endpoints specified in the ALB Target Groups.
Type
CRD
Group
alb.yandex-cloud.jet.crossplane.io
Version
v1alpha1
apiVersion: alb.yandex-cloud.jet.crossplane.io/v1alpha1
kind: LoadBalancer
LoadBalancerSpec defines the desired state of LoadBalancer
No description provided.
Allocation zones for the Load Balancer instance. The structure is documented below.
Unique set of locations. The structure is documented below.
Reference to a Subnet in vpc to populate subnetId.
Policies for referencing.
Selector for a Subnet in vpc to populate subnetId.
Policies for selection.
Reference to a Folder in resourcemanager to populate folderId.
Policies for referencing.
Selector for a Folder in resourcemanager to populate folderId.
Policies for selection.
List of listeners for the Load Balancer. The structure is documented below.
Network endpoints (addresses and ports) of the listener. The structure is documented below.
Provided by the client or computed automatically.
External IPv4 address. The structure is documented below.
External IPv6 address. The structure is documented below.
Internal IPv4 address. The structure is documented below.
Reference to a Subnet in vpc to populate subnetId.
Policies for referencing.
Selector for a Subnet in vpc to populate subnetId.
Policies for selection.
One or more ports to listen on.
HTTP listener resource. The structure is documented below.
Stream handler that sets plaintext Stream backend group. The structure is documented below.
If set, will enable HTTP2 protocol for the handler. The structure is documented below.
Reference to a HTTPRouter to populate httpRouterId.
Policies for referencing.
Selector for a HTTPRouter to populate httpRouterId.
Policies for selection.
Shortcut for adding http -> https redirects. The structure is documented below.
Stream listener resource. The structure is documented below.
Stream handler that sets plaintext Stream backend group. The structure is documented below.
TLS listener resource. The structure is documented below.
TLS handler resource. The structure is documented below.
Certificate IDs in the Certificate Manager. Multiple TLS certificates can be associated with the same context to allow both RSA and ECDSA certificates. Only the first certificate of each type will be used.
HTTP handler resource. The structure is documented below.
If set, will enable HTTP2 protocol for the handler. The structure is documented below.
Stream handler resource. The structure is documented below.
SNI match resource. The structure is documented below.
Stream handler that sets plaintext Stream backend group. The structure is documented below.
Certificate IDs in the Certificate Manager. Multiple TLS certificates can be associated with the same context to allow both RSA and ECDSA certificates. Only the first certificate of each type will be used.
HTTP handler resource. The structure is documented below.
If set, will enable HTTP2 protocol for the handler. The structure is documented below.
Stream handler resource. The structure is documented below.
A set of server names.
Cloud Logging settings. The structure is documented below.
List of rules to discard a fraction of logs. The structure is documented below.
list of grpc codes by name, e.g, ["NOT_FOUND", "RESOURCE_EXHAUSTED"]
5XX or ALL
599
Reference to a Network in vpc to populate networkId.
Policies for referencing.
Selector for a Network in vpc to populate networkId.
Policies for selection.
A list of ID's of security groups attached to the Load Balancer.
References to SecurityGroup in vpc to populate securityGroupIds.
Policies for referencing.
Selector for a list of SecurityGroup in vpc to populate securityGroupIds.
Policies for selection.
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.
Allocation zones for the Load Balancer instance. The structure is documented below.
Unique set of locations. The structure is documented below.
Reference to a Subnet in vpc to populate subnetId.
Policies for referencing.
Selector for a Subnet in vpc to populate subnetId.
Policies for selection.
Reference to a Folder in resourcemanager to populate folderId.
Policies for referencing.
Selector for a Folder in resourcemanager to populate folderId.
Policies for selection.
List of listeners for the Load Balancer. The structure is documented below.
Network endpoints (addresses and ports) of the listener. The structure is documented below.
Provided by the client or computed automatically.
External IPv4 address. The structure is documented below.
External IPv6 address. The structure is documented below.
Internal IPv4 address. The structure is documented below.
Reference to a Subnet in vpc to populate subnetId.
Policies for referencing.
Selector for a Subnet in vpc to populate subnetId.
Policies for selection.
One or more ports to listen on.
HTTP listener resource. The structure is documented below.
Stream handler that sets plaintext Stream backend group. The structure is documented below.
If set, will enable HTTP2 protocol for the handler. The structure is documented below.
Reference to a HTTPRouter to populate httpRouterId.
Policies for referencing.
Selector for a HTTPRouter to populate httpRouterId.
Policies for selection.
Shortcut for adding http -> https redirects. The structure is documented below.
Stream listener resource. The structure is documented below.
Stream handler that sets plaintext Stream backend group. The structure is documented below.
TLS listener resource. The structure is documented below.
TLS handler resource. The structure is documented below.
Certificate IDs in the Certificate Manager. Multiple TLS certificates can be associated with the same context to allow both RSA and ECDSA certificates. Only the first certificate of each type will be used.
HTTP handler resource. The structure is documented below.
If set, will enable HTTP2 protocol for the handler. The structure is documented below.
Stream handler resource. The structure is documented below.
SNI match resource. The structure is documented below.
Stream handler that sets plaintext Stream backend group. The structure is documented below.
Certificate IDs in the Certificate Manager. Multiple TLS certificates can be associated with the same context to allow both RSA and ECDSA certificates. Only the first certificate of each type will be used.
HTTP handler resource. The structure is documented below.
If set, will enable HTTP2 protocol for the handler. The structure is documented below.
Stream handler resource. The structure is documented below.
A set of server names.
Cloud Logging settings. The structure is documented below.
List of rules to discard a fraction of logs. The structure is documented below.
list of grpc codes by name, e.g, ["NOT_FOUND", "RESOURCE_EXHAUSTED"]
5XX or ALL
599
Reference to a Network in vpc to populate networkId.
Policies for referencing.
Selector for a Network in vpc to populate networkId.
Policies for selection.
A list of ID's of security groups attached to the Load Balancer.
References to SecurityGroup in vpc to populate securityGroupIds.
Policies for referencing.
Selector for a list of SecurityGroup in vpc to populate securityGroupIds.
Policies for selection.
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.
LoadBalancerStatus defines the observed state of LoadBalancer.
No description provided.
Allocation zones for the Load Balancer instance. The structure is documented below.
Unique set of locations. The structure is documented below.
List of listeners for the Load Balancer. The structure is documented below.
Network endpoints (addresses and ports) of the listener. The structure is documented below.
Provided by the client or computed automatically.
External IPv4 address. The structure is documented below.
External IPv6 address. The structure is documented below.
One or more ports to listen on.
HTTP listener resource. The structure is documented below.
Stream handler that sets plaintext Stream backend group. The structure is documented below.
If set, will enable HTTP2 protocol for the handler. The structure is documented below.
Shortcut for adding http -> https redirects. The structure is documented below.
Stream listener resource. The structure is documented below.
Stream handler that sets plaintext Stream backend group. The structure is documented below.
TLS listener resource. The structure is documented below.
TLS handler resource. The structure is documented below.
Certificate IDs in the Certificate Manager. Multiple TLS certificates can be associated with the same context to allow both RSA and ECDSA certificates. Only the first certificate of each type will be used.
HTTP handler resource. The structure is documented below.
If set, will enable HTTP2 protocol for the handler. The structure is documented below.
Stream handler resource. The structure is documented below.
SNI match resource. The structure is documented below.
Stream handler that sets plaintext Stream backend group. The structure is documented below.
Certificate IDs in the Certificate Manager. Multiple TLS certificates can be associated with the same context to allow both RSA and ECDSA certificates. Only the first certificate of each type will be used.
HTTP handler resource. The structure is documented below.
If set, will enable HTTP2 protocol for the handler. The structure is documented below.
Stream handler resource. The structure is documented below.
A set of server names.
Cloud Logging settings. The structure is documented below.
List of rules to discard a fraction of logs. The structure is documented below.
list of grpc codes by name, e.g, ["NOT_FOUND", "RESOURCE_EXHAUSTED"]
5XX or ALL
599
A list of ID's of security groups attached to the Load Balancer.
Conditions of the resource.
test-balancer
apiVersion: alb.yandex-cloud.jet.crossplane.io/v1alpha1
kind: LoadBalancer
metadata:
annotations:
meta.upbound.io/example-id: alb/v1alpha1/loadbalancer
labels:
testing.upbound.io/example-name: test-balancer
name: test-balancer
spec:
forProvider:
allocationPolicy:
- location:
- subnetIdRef:
name: example-subnet-a
zoneId: ru-central1-a
listener:
- endpoint:
- address:
- externalIpv4Address:
- {}
ports:
- 8080
http:
- handler:
- httpRouterIdRef:
name: test-router
name: my-listener
name: my-load-balancer
networkIdRef:
name: example-net
providerConfigRef:
name: default