LB is the Schema for the LBs API. Provides a Load Balancer resource.
Type
CRD
Group
elbv2.aws.upbound.io
Version
v1beta1
apiVersion: elbv2.aws.upbound.io/v1beta1
kind: LB
LBSpec defines the desired state of LB
No description provided.
An Access Logs block. Access Logs documented below.
Reference to a Bucket in s3 to populate bucket.
Policies for referencing.
Selector for a Bucket in s3 to populate bucket.
Policies for selection.
References to SecurityGroup in ec2 to populate securityGroups.
Policies for referencing.
Selector for a list of SecurityGroup in ec2 to populate securityGroups.
Policies for selection.
A list of security group IDs to assign to the LB. Only valid for Load Balancers of type application or network. For load balancers of type network security groups cannot be added if none are currently present, and cannot all be removed once added. If either of these conditions are met, this will force a recreation of the resource.
A subnet mapping block as documented below. For Load Balancers of type network subnet mappings can only be added.
Reference to a Subnet in ec2 to populate subnetId.
Policies for referencing.
Selector for a Subnet in ec2 to populate subnetId.
Policies for selection.
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.
A list of subnet IDs to attach to the LB. For Load Balancers of type network subnets can only be added (see Availability Zones), deleting a subnet for load balancers of type network will force a recreation of the resource.
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.
An Access Logs block. Access Logs documented below.
Reference to a Bucket in s3 to populate bucket.
Policies for referencing.
Selector for a Bucket in s3 to populate bucket.
Policies for selection.
References to SecurityGroup in ec2 to populate securityGroups.
Policies for referencing.
Selector for a list of SecurityGroup in ec2 to populate securityGroups.
Policies for selection.
A list of security group IDs to assign to the LB. Only valid for Load Balancers of type application or network. For load balancers of type network security groups cannot be added if none are currently present, and cannot all be removed once added. If either of these conditions are met, this will force a recreation of the resource.
A subnet mapping block as documented below. For Load Balancers of type network subnet mappings can only be added.
Reference to a Subnet in ec2 to populate subnetId.
Policies for referencing.
Selector for a Subnet in ec2 to populate subnetId.
Policies for selection.
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.
A list of subnet IDs to attach to the LB. For Load Balancers of type network subnets can only be added (see Availability Zones), deleting a subnet for load balancers of type network will force a recreation of the resource.
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.
LBStatus defines the observed state of LB.
No description provided.
A list of security group IDs to assign to the LB. Only valid for Load Balancers of type application or network. For load balancers of type network security groups cannot be added if none are currently present, and cannot all be removed once added. If either of these conditions are met, this will force a recreation of the resource.
A subnet mapping block as documented below. For Load Balancers of type network subnet mappings can only be added.
A list of subnet IDs to attach to the LB. For Load Balancers of type network subnets can only be added (see Availability Zones), deleting a subnet for load balancers of type network will force a recreation of the resource.
Conditions of the resource.
test
apiVersion: elbv2.aws.upbound.io/v1beta1
kind: LB
metadata:
labels:
testing.upbound.io/example-name: elbv2
name: test
spec:
forProvider:
enableDeletionProtection: false
internal: false
loadBalancerType: application
name: test-lb-tf
region: us-west-1
securityGroupSelector:
matchLabels:
testing.upbound.io/example-name: elbv2
subnetSelector:
matchLabels:
testing.upbound.io/example-name: elbv2
tags:
Environment: production
front-end
apiVersion: elbv2.aws.upbound.io/v1beta1
kind: LB
metadata:
annotations:
meta.upbound.io/example-id: elbv2/v1beta1/lblistenerrule
labels:
testing.upbound.io/example-name: front_end
name: front-end
spec:
forProvider:
region: us-west-1
securityGroupSelector:
matchLabels:
testing.upbound.io/example-name: elbv2
subnetMapping:
- subnetIdSelector:
matchLabels:
testing.upbound.io/example-name: elbv2
- subnetIdSelector:
matchLabels:
testing.upbound.io/example-name: elbv2s2
example
apiVersion: elbv2.aws.upbound.io/v1beta1
kind: LB
metadata:
annotations:
meta.upbound.io/example-id: elbv2/v1beta1/lblistenercertificate
upjet.upbound.io/manual-intervention: This resource is skipping because the parent resource was skipped.
labels:
testing.upbound.io/example-name: lb
name: example
spec:
forProvider:
region: us-west-1
securityGroupSelector:
matchLabels:
testing.upbound.io/example-name: elbv2
subnetMapping:
- subnetIdSelector:
matchLabels:
testing.upbound.io/example-name: elbv2
- subnetIdSelector:
matchLabels:
testing.upbound.io/example-name: elbv2s2
example
apiVersion: elbv2.aws.upbound.io/v1beta1
kind: LB
metadata:
labels:
testing.upbound.io/example-name: vpclink
name: example
spec:
forProvider:
internal: true
loadBalancerType: network
name: example-lb-${Rand.RFC1123Subdomain}
region: us-west-1
subnetMapping:
- subnetIdSelector:
matchLabels:
testing.upbound.io/example-name: vpclink
© 2022 Upbound, Inc.
Discover the building blocksfor your internal cloud platform.