LoadBalancer is the Schema for the LoadBalancers API
Type
CRD
Group
elbv2.aws.crossplane.io
Version
v1alpha1
apiVersion: elbv2.aws.crossplane.io/v1alpha1
kind: LoadBalancer
LoadBalancerSpec defines the desired state of LoadBalancer
LoadBalancerParameters defines the desired state of LoadBalancer
Reference to Security Groups for SecurityGroups field
Policies for referencing.
Selector for references to SecurityGroups
Policies for selection.
[Application Load Balancers and Network Load Balancers] The IDs of the security groups for the load balancer.
The IDs of the public subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings, but not both.
[Application Load Balancers] You must specify subnets from at least two Availability Zones. You cannot specify Elastic IP addresses for your subnets.
[Application Load Balancers on Outposts] You must specify one Outpost subnet.
[Application Load Balancers on Local Zones] You can specify subnets from one or more Local Zones.
[Network Load Balancers] You can specify subnets from one or more Availability Zones. You can specify one Elastic IP address per subnet if you need static IP addresses for your internet-facing load balancer. For internal load balancers, you can specify one private IP address per subnet from the IPv4 range of the subnet. For internet-facing load balancer, you can specify one IPv6 address per subnet.
[Gateway Load Balancers] You can specify subnets from one or more Availability Zones. You cannot specify Elastic IP addresses for your subnets.
Reference to Subnets for Subnets field
Policies for referencing.
Selector for references to Subnets
Policies for selection.
The IDs of the public subnets. You can specify only one subnet per Availability Zone. You must specify either subnets or subnet mappings, but not both. To specify an Elastic IP address, specify subnet mappings instead of subnets.
[Application Load Balancers] You must specify subnets from at least two Availability Zones.
[Application Load Balancers on Outposts] You must specify one Outpost subnet.
[Application Load Balancers on Local Zones] You can specify subnets from one or more Local Zones.
[Network Load Balancers] You can specify subnets from one or more Availability Zones.
[Gateway Load Balancers] You can specify subnets from one or more Availability Zones.
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.
LoadBalancerObservation defines the observed state of LoadBalancer
Conditions of the resource.
gatewayloadbalancer
apiVersion: elbv2.aws.crossplane.io/v1alpha1
kind: LoadBalancer
metadata:
name: gatewayloadbalancer
spec:
forProvider:
loadBalancerType: gateway
name: gatewayloadbalancer
region: us-east-1
subnetRefs:
- name: sample-subnet1
- name: sample-subnet2
providerConfigRef:
name: example
test-loadbalancer
apiVersion: elbv2.aws.crossplane.io/v1alpha1
kind: LoadBalancer
metadata:
name: test-loadbalancer
spec:
forProvider:
loadBalancerType: application
name: test-loadbalancer
region: us-east-1
securityGroupRefs:
- name: sample-cluster-sg
subnetRefs:
- name: sample-subnet1
- name: sample-subnet2
providerConfigRef:
name: example