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.
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