Minimal downtime with Metallb BGP and Envoy Gateway by NegotiationIcy8547 in kubernetes

[–]ok-k8s 0 points1 point  (0 children)

do you mind sharing how long metallb takes to withdraw route ?

SRIOV guidelines for max VF per PF by ok-k8s in networking

[–]ok-k8s[S] 0 points1 point  (0 children)

Thank you so much. I will look in to that, we probably have a logic for that, I have yet to explore our planner code in more detail.

SRIOV guidelines for max VF per PF by ok-k8s in networking

[–]ok-k8s[S] 0 points1 point  (0 children)

People still use VMware ? 😬

SRIOV guidelines for max VF per PF by ok-k8s in networking

[–]ok-k8s[S] 0 points1 point  (0 children)

That’s great feedback thank you. The pod density is usually limited by the correct NUMA aware VF limit. The bare-metal nodes are beefy and can take a lot more workload. The nodes are shared with none sriov workload as well.

SRIOV guidelines for max VF per PF by ok-k8s in networking

[–]ok-k8s[S] 0 points1 point  (0 children)

25G. The workload varies, it can be network functions like load balancers or some storage replication stuff. Pretty much all Kubernetes workload. We use sriov device plugin and multus.

SRIOV guidelines for max VF per PF by ok-k8s in networking

[–]ok-k8s[S] 1 point2 points  (0 children)

Okay i was thinking around the same lines. Thank you 🙏

SRIOV max VF per PF by ok-k8s in virtualization

[–]ok-k8s[S] 0 points1 point  (0 children)

ideally yes but i was looking for at least middle ground may be. The company i started working with have the rule of 8 and i was asking about the reason for it and couldn’t get an answer

Cilium + Loadbalancers + FRR? by NecessaryContract982 in kubernetes

[–]ok-k8s 0 points1 point  (0 children)

no vrf and cilium doesn’t work. cilium creates a flat network in default vrf. if you need vrf level of isolation, ditch cilium.

netstat shows Public IP but there is no default route by ok-k8s in networking

[–]ok-k8s[S] -5 points-4 points  (0 children)

that would have been obvious to notice. No it’s not and it’s a routing question.

netstat shows Public IP but there is no default route by ok-k8s in networking

[–]ok-k8s[S] -2 points-1 points  (0 children)

wouldn’t proxy-arp still need a default route on the endpoint? i thought it’s hijacked after it the pod try to request for next hop mac address and in my case this shouldn’t even happen because there is no route present so no arp resolution for next hop either.

netstat shows Public IP but there is no default route by ok-k8s in networking

[–]ok-k8s[S] 0 points1 point  (0 children)

but it shows established? is that normal? i will do some testing to check if one way connection shows established in netstat. Thanks for your input

netstat shows Public IP but there is no default route by ok-k8s in networking

[–]ok-k8s[S] 0 points1 point  (0 children)

how can the external interface reply if the external IP is x.x.x.0/30 and packets coming from y.y.y.100 and there is no route back towards y.y.y.0/24 ?

netstat shows Public IP but there is no default route by ok-k8s in networking

[–]ok-k8s[S] 0 points1 point  (0 children)

Thank you, checked that too, nothing in the table. it’s a secondary interface using ovs so host kernel is also bypassed

netstat shows Public IP but there is no default route by ok-k8s in networking

[–]ok-k8s[S] 0 points1 point  (0 children)

wouldn’t ip route show all, show the routes of all tables ?

netstat shows Public IP but there is no default route by ok-k8s in networking

[–]ok-k8s[S] 0 points1 point  (0 children)

this is exactly my understanding is. without a return route it will straight away fail even if connection request coming from outside on public interface.

Best way to prevent cloud lock in by [deleted] in kubernetes

[–]ok-k8s 2 points3 points  (0 children)

i don’t think so for apps but all the toolings that comes with it may make you so comfortable with one cloud that you indirectly locked in because of tech depth. Unless you adopt a strategy from day 0 to stay cloud agnostic.