-
Notifications
You must be signed in to change notification settings - Fork 26
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
Use cloud-provider-kind instead of MetalLB #1622
base: devel
Are you sure you want to change the base?
Conversation
kind has a cloud-provider which can take care of LoadBalancer-type services; this works fine with LB-mode Submariner, so use that instead of MetalLB. Currently the command is installed as cmd, which is why it is renamed during container construction. This is fixed for the next release of the cloud-provider. cloud-provider-kind runs in the foreground, so this wraps it in a container run alongside the kind clusters, on the host network. The container is stopped on cleanup. The dependency version will be tracked using dependabot. Signed-off-by: Stephen Kitt <skitt@redhat.com>
🤖 Created branch: z_pr1622/skitt/cloud-provider-kind |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice!
Switching to draft because this leaves haproxy containers running (and shouldn’t). |
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further |
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further |
I think we should consider keeping MetalLB as well since it is the default LB provider for baremetal. Do you think we can support both methods? |
kind has a cloud-provider which can take care of LoadBalancer-type services; this works fine with LB-mode Submariner, so use that instead of MetalLB.
Currently the command is installed as cmd, which is why it is renamed during container construction. This is fixed for the next release of the cloud-provider.
cloud-provider-kind runs in the foreground, so this wraps it in a container run alongside the kind clusters, on the host network. The container is stopped on cleanup.
The dependency version will be tracked using dependabot.