We use cloudstack, but don't use cloudstack loadbalancers for our Kubernetes cluster.
How do we prevent Cloudstack Kubernetes provider from interfering with our existing "Service" resources that are already exposed as type "LoadBalancer"?
We would like to:
- Either disable loadbalancer allocation completely
- Or only allocate Loadbalancer when a certain annotation or label is set on the "Service" object.
We still want to use the CloudStack Controller for our node labeling (region, failure-domain, etc..)
We use cloudstack, but don't use cloudstack loadbalancers for our Kubernetes cluster.
How do we prevent Cloudstack Kubernetes provider from interfering with our existing "Service" resources that are already exposed as type "LoadBalancer"?
We would like to:
We still want to use the CloudStack Controller for our node labeling (region, failure-domain, etc..)