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

Support both an internal and external API server endpoint #4755

Open
nrb opened this issue Apr 19, 2024 · 1 comment
Open

Support both an internal and external API server endpoint #4755

nrb opened this issue Apr 19, 2024 · 1 comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@nrb
Copy link

nrb commented Apr 19, 2024

/kind feature

Describe the solution you'd like

We'd like to use CAPZ within OpenShift, and currently, we support dual endpoints in our clusters. One is external for use with tools like kubectl from user laptops. The other is internal, for traffic between controllers/kubelets and the API server.

It looks like CAPZ already supports an external load balancer for private clusters, but this is egress only. For our use, we would like to create one that also allows ingress.

Anything else you would like to add:

We (Red Hat) would happily take on this work, so long as we know it is acceptable by the maintainers.

@k8s-ci-robot k8s-ci-robot added the kind/feature Categorizes issue or PR as related to a new feature. label Apr 19, 2024
@mboersma
Copy link
Contributor

We discussed this at CAPZ office hours and think it would be a big improvement. We'd love to work with your contribution, thanks!

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.
Projects
Status: No status
Development

No branches or pull requests

3 participants