Currently exploring options to replace ingress nginx and at the same time k8s ingress kind with gateway api. This requirement may be achieved using a cloud vendor solution like aws load balancer controller and application load balancer and in the main exchange ingress resource kind for httproute (oversimplified).
In addition to the requirements it would also make sense to review how east-west traffic is secured; this is where linkerd comes in.
I am struggling to find documentation that explains how linkerd may be used to control east-west traffic flows and how it may integrate with other gateway api gateways for north-south; please help
In terms of “control east-west traffic flows” you may have to be a little more specific about what kind of control you’re after… there are a lot of features that Linkerd provides here.
Great link for ingress kind; is there support for gateway api kinds?
In terms of east-west traffic control we were looking to restrict which pods in a cluster may communicate with other services/ pods in the same cluster. Ideally implement the equivalent of network policy but have visibility over which services talk within a cluster before enforcing any restrictions.
What would be the consequence of implementing a gateway and httproute kinds that have no integration with your product? For example, can you simply allow all north-south traffic and then use your product to control internal east-west traffic?
