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.

Sign up for GitHub

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

Jump to bottom

APIServer for internode communication should be defined as a separate spec #5313

Open
nawazkh opened this issue Nov 26, 2024 · 0 comments
Open

APIServer for internode communication should be defined as a separate spec #5313

nawazkh opened this issue Nov 26, 2024 · 0 comments
Labels
kind/proposal Issues or PRs related to proposals. priority/backlog Higher priority than priority/awaiting-more-evidence.

Comments

@nawazkh
Copy link
Member

nawazkh commented Nov 26, 2024 •
edited
Loading

APIServerILB feature introduces an Internal LB thats sharing the configuration of a Public API Server LB spec.
Ideally, we would like to have the internal API Server LB as a separate spec field in the AzureCluster spec.
@nawazkh nawazkh mentioned this issue Nov 26, 2024
Open
@nawazkh nawazkh added the kind/proposal Issues or PRs related to proposals. label Jan 23, 2025
@nawazkh nawazkh added the priority/backlog Higher priority than priority/awaiting-more-evidence. label Feb 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/proposal Issues or PRs related to proposals. priority/backlog Higher priority than priority/awaiting-more-evidence.
Projects
CAPZ Planning
Status: Todo
Milestone
No milestone
Development

No branches or pull requests
1 participant
@nawazkh