ELB is the Schema for the ELBs API. Provides an Elastic Load Balancer resource.
Type
CRD
Group
elb.aws.upbound.io
Version
v1beta1
apiVersion: elb.aws.upbound.io/v1beta1
kind: ELB
ELBSpec defines the desired state of ELB
No description provided.
An Access Logs block. Access Logs documented below.
The AZ's to serve traffic in.
A health_check block. Health Check documented below.
A list of instance ids to place in the ELB pool.
References to Instance in ec2 to populate instances.
Policies for referencing.
Selector for a list of Instance in ec2 to populate instances.
Policies for selection.
A list of listener blocks. Listeners documented below.
A list of security group IDs to assign to the ELB. Only valid if creating an ELB within a VPC
A list of subnet IDs to attach to the ELB.
References to Subnet in ec2 to populate subnets.
Policies for referencing.
Selector for a list of Subnet in ec2 to populate subnets.
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.
ELBStatus defines the observed state of ELB.
Conditions of the resource.
example
apiVersion: elb.aws.upbound.io/v1beta1
kind: ELB
metadata:
name: example
spec:
forProvider:
connectionDraining: true
connectionDrainingTimeout: 400
crossZoneLoadBalancing: true
healthCheck:
- healthyThreshold: 2
interval: 30
target: HTTP:8000/
timeout: 3
unhealthyThreshold: 2
idleTimeout: 400
listener:
- instancePort: 8000
instanceProtocol: http
lbPort: 80
lbProtocol: http
region: us-west-1
subnetsRefs:
- name: sample-subnet1
- name: sample-subnet2
© 2022 Upbound, Inc.
Discover the building blocksfor your internal cloud platform.