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
I suggest having Expect() take a pair of interface arguments for the source and dest. In the felix FVs I quickly found that I wanted to expand on the types of source and dest that the connectivity checked could handle. The first time I did that, I added a new optional arg to ExpectSome/ExpectNone (for the destination port) but I regretted that decision as soon as the next variant came along.
In k8s, I expect we'll want destination types that include: pods, host-networked pods, nodeports, service IPs, external IPs(?), etc.
The text was updated successfully, but these errors were encountered:
from slack: (shaun crampton, project calico)
I suggest having Expect() take a pair of interface arguments for the source and dest. In the felix FVs I quickly found that I wanted to expand on the types of source and dest that the connectivity checked could handle. The first time I did that, I added a new optional arg to ExpectSome/ExpectNone (for the destination port) but I regretted that decision as soon as the next variant came along.
In k8s, I expect we'll want destination types that include: pods, host-networked pods, nodeports, service IPs, external IPs(?), etc.
The text was updated successfully, but these errors were encountered: