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

LoadBalancer Requirement For None / BareMetal #5148

Open
timway opened this issue Nov 18, 2024 · 1 comment
Open

LoadBalancer Requirement For None / BareMetal #5148

timway opened this issue Nov 18, 2024 · 1 comment
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@timway
Copy link

timway commented Nov 18, 2024

I built a cluster in the OpenShift UI with a single worker node using IPMI (redfish-virtualmedia). It appears to have set the platform type to None. Reading the documentation it indicated I needed a load balancer like MetalLB to get access to services running on the data plane or worker node(s). If I deploy MetalLB I do in fact get access to services. My question is why isn't ingressVips used so this works out of the box?

Prior to deploying MetallLB I see the default ingress controller and I see it configured for a HostNetwork endpoint publishing strategy. If I curl the worker node IP the router is running (only 1 worker node in my case) for a known app like curl --insecure --verbose --header "Host: console-openshift-console.<cluster>.<base>" https://<worker-node-ip> I do in fact get the console back.

A side-effect of this is the OpenShift UI provides a link to OpenShift console that is dead on arrival. An administrator has to deploy and configure MetalLB in the cluster using CLI and then configure the *.apps.<cluster>.<base> wildcard after the fact. Leaving the feature feeling clunky out of the box. I'd have been less confused if the link wasn't shown.

@openshift-bot
Copy link

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

2 participants