You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not sure if this is already implemented, the k3s documentation only mentions one pool per node
but it would be cool to attribute a node to be available in several pools
i have made pools based on what should be exposed on specific nodes,
one node can expose several load balancer serviçes, while other nodes only expose some...
i made affinity so my load balancer workloads schedule on specific svccontroller.k3s.cattle.io/lbpool labeled pods, so it matches the externalTrafficPolicy: Local policy
The text was updated successfully, but these errors were encountered:
Not sure if this is already implemented, the k3s documentation only mentions one pool per node
but it would be cool to attribute a node to be available in several pools
example: svccontroller.k3s.cattle.io/lbpool='["pool1","pool2"]' || svccontroller.k3s.cattle.io/lbpool='pool1,pool2'
would that be possible?
i have made pools based on what should be exposed on specific nodes,
one node can expose several load balancer serviçes, while other nodes only expose some...
i made affinity so my load balancer workloads schedule on specific svccontroller.k3s.cattle.io/lbpool labeled pods, so it matches the
externalTrafficPolicy: Local
policyThe text was updated successfully, but these errors were encountered: