[FEATURE] Expose the IPMI endpoint to external

[starbops]

Is your feature request related to a problem? Please describe.

To be able to access the KubeBMC for a specific VM, users are required to have the ability and rights to access the cluster. This is because the IPMI endpoints are currently exposed through ClusterIP type of Services. The only way to touch the endpoint is to spawn Pods on the cluster. It isn't very easy for external users or applications to integrate with KubeBMC. They still have to be aware of Kubernetes.

Describe the solution you'd like

Leverage NodePort or LoadBalancer type of Services, which can provide external accessibility.

Describe alternatives you've considered

Build up a new program responsible for proxying all the IPMI access requests from external to the internal KubeBMC endpoints.

Additional context

N/A

[starbops]

So the plan is to add a simple toggle under the VirtualMachineBMC CRD's .spec section for users to specify whether to expose the BMC to the outside world with the aid of the load balancer provider, e.g., kube-vip. Also, a corresponding field will be under the .status section that reflects the provisioned external IP.

That being said, I'm still unsure if we should integrate a specific load balancer solution or not...

[starbops]

To make it work in the current implementation, you need to manually modify the generated Service object. It depends on your environment's solutions.

Suppose you have kube-vip deployed in your cluster (along with KubeVirtBMC). In that case, you can simply modify the generated Service object from the ClusterIP type to the LoadBalancer type and also add a loadBalancerIP: 0.0.0.0 to the .spec section. This will make kube-vip grab an IP address with DHCP (needless to say, you'll need a valid DHCP server running on the network).

[ibrokethecloud]

we could define an annotation on VM to control if virtualmachinebmc service needs to be of type loadbalancer