Open nrb opened 6 months ago
We discussed this at CAPZ office hours and think it would be a big improvement. We'd love to work with your contribution, thanks!
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle rotten
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
/remove-lifecycle rotten
I think @jhixson74 is going to be looking at this from our side.
/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.