Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bring your own control plane ELB #2774

Closed
dlipovetsky opened this issue Sep 20, 2021 · 2 comments · Fixed by #2787
Closed

Bring your own control plane ELB #2774

dlipovetsky opened this issue Sep 20, 2021 · 2 comments · Fixed by #2787
Assignees
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

Comments

@dlipovetsky
Copy link
Contributor

/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.

@k8s-ci-robot k8s-ci-robot added kind/feature Categorizes issue or PR as related to a new feature. needs-priority labels Sep 20, 2021
@shivi28
Copy link
Contributor

shivi28 commented Sep 21, 2021

Thanks @dlipovetsky for raising the detailed use case.
We have an on-going proposal for Load balancer provider and I will check if we can address this use case as part of that proposal.

@richardcase
Copy link
Member

As there is a PR open:

/assign dlipovetsky
/lifecycle active

@k8s-ci-robot k8s-ci-robot added the lifecycle/active Indicates that an issue or PR is actively being worked on by a contributor. label Sep 29, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants