Bring your own control plane ELB #2774
Labels
kind/feature
Categorizes issue or PR as related to a new feature.
lifecycle/active
Indicates that an issue or PR is actively being worked on by a contributor.
needs-priority
/kind feature
Describe the solution you'd like
I am creating a CAPA cluster using existing AWS infrastructure. I have an existing ELB that I want CAPA to use.
Anything else you would like to add:
The ELB name is not part of the AWSCluster spec. The AWSCluster controller derives the ELB name from the cluster name.
It appears possible to make the ELB name part of the AWSCluster spec. The user can provide a value. If the user does not provide a value, CAPA will derive a value from the cluster name, as it does today, and write it to the spec. The AWSCluster validation webhook can ensure that the ELB name is written at most one time, in the way it does for the controlPlaneEndpoint field.
The text was updated successfully, but these errors were encountered: