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
The issue comes when a LoadBalancer Service gets created and wants to request an IP in the vlan201-external-subnet Subnet. If the lb-svc-* Pod gets scheduled on a non-kube-ovn master node, it fails to get an IP. Manually editing the Deployment and specifying a nodeSelector fixes this issue:
nodeSelector:
kube-ovn/role: master
kubernetes.io/os: linux
Is there already a way to specify this nodeSelector? Looking at the source code, it does not seem to be the case:
maybe make it just the same as the vpc-nat-gw pod is a better way
It really is the simple and reasonable way to resolve this problem.
The vpc-nat-gw pod is created by vpc-nat-gateways crd, and there's selector fields in vpc-nat-gateways crd,so it's easy to pass nodeSelector values to pod.
What we need is same as vpc-nat-gw, the nodeSelector field for lb-svc, but there's no crd field to pass this value.
As the image for lb-svc is configured in configmap ovn-vpc-nat-config, so maybe it's a good way to put nodeSelector in the same configmap as follows
Description
Hi Everyone,
In our setup, we have VLAN interfaces that are only available/configured on the Kubernetes Master Nodes.
The following
NetworkAttachmentDefinition
has been created:The
VpcNatGateway
is deployed with the followingselector
, which forces it to run onkube-ovn
masters:The issue comes when a
LoadBalancer
Service gets created and wants to request an IP in thevlan201-external-subnet
Subnet. If thelb-svc-*
Pod gets scheduled on a non-kube-ovn
master node, it fails to get an IP. Manually editing theDeployment
and specifying anodeSelector
fixes this issue:Is there already a way to specify this
nodeSelector
? Looking at the source code, it does not seem to be the case:kube-ovn/pkg/controller/service_lb.go
Lines 104 to 139 in 06ac37d
Thanks in advance for your support!
Who will benefit from this feature?
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: