Closed TimTinneveld closed 1 year ago
Right now we have made the change to put only worker nodes into the pool. @TimTinneveld can you check if this is sufficient for you?
Hi @arunmk,
That would be perfect.
I guess this will be available in 1.0 version?
@TimTinneveld sorry for the delay in response - I believe this is issue should have been opened against https://github.com/vmware/cloud-provider-for-cloud-director.
Is your feature request related to a problem? Please describe.
When i am creating for example an ingress controller, it selects all the machines in the Kubernetes cluster for the alb server pool. Most of the time i create the ingress on one worker or all of the workers, i never install workload pods on the masters. Putting the masters also in the pool of the loadbalancer gonna make the ingress really slow because the master doesn't respond. The master nodes does not have the required pods running.
I also don't want workload to be loadbalanced over the masters.
Describe the solution you'd like
Having an option to choose which nodes to put in the server pool of the loadbalancer, for example of Annotations/Label.
By default only putting the worker nodes in the pool. Most of the time you only use the workers for workload. Having the master nodes automatically also in the pool is not necessary for me.
Describe alternatives you've considered
For now i edit the pool by hand in the vcd console.
Additional context
No response