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

Change API to use a separate Kind for load balancer #35

Open
richardcase opened this issue Nov 23, 2021 · 1 comment
Open

Change API to use a separate Kind for load balancer #35

richardcase opened this issue Nov 23, 2021 · 1 comment
Labels
kind/feature New feature or request priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.

Comments

@richardcase
Copy link
Member

Describe the solution you'd like:
The cluster template currently sets the control plane endpoint before the api server load balancer is available, this causes errors in the CAPI controllers.

Change to a separate kind for a load balancer and only populate the contriol plane endpoint when its available.

Why do you want this feature:

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

@richardcase richardcase added the kind/feature New feature or request label Nov 23, 2021
@richardcase richardcase added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Dec 2, 2021
@github-actions
Copy link

github-actions bot commented Feb 1, 2022

This issue is stale because it has been open 60 days with no activity.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 1, 2022
@Callisto13 Callisto13 removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature New feature or request priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
No open projects
Status: Backlog
Development

No branches or pull requests

2 participants