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 am about to setup linkerd-based authentication for ingresses as well as for services.
this chart seems to be a nice generic way to handle linkerd-internal traffic and ingress traffic.
I see the NetworkAuthentication object cluster-network-authn, but no reference in an AuthorizationPolicy. Does the NetworkAuthentication without reference have an effect?
Second question is about the ingress handling. I have two types of ingresses and ingress controllers:
nginx ingress controller which generated an aws network loadbalancer and a pod in another namespace which is not managed by linkerd, communication: external network -> aws network loadbalancer -> pod of ingress controller -> pod of application
aws-load-balancer-controller which generates an aws application loadbalancer, communication: external network -> ws application loadbalancer -> pod of application
Do you support both types of ingresses?
I see only the AuthorizationPolicy linkerd-ingress-allow with MeshTLSAuthentication which could support my nginx-ingress-controller ingresses.
Best...
Uwe
The text was updated successfully, but these errors were encountered:
Hi,
I am about to setup linkerd-based authentication for ingresses as well as for services.
this chart seems to be a nice generic way to handle linkerd-internal traffic and ingress traffic.
I see the NetworkAuthentication object cluster-network-authn, but no reference in an AuthorizationPolicy. Does the NetworkAuthentication without reference have an effect?
Second question is about the ingress handling. I have two types of ingresses and ingress controllers:
Do you support both types of ingresses?
I see only the AuthorizationPolicy linkerd-ingress-allow with MeshTLSAuthentication which could support my nginx-ingress-controller ingresses.
Best...
Uwe
The text was updated successfully, but these errors were encountered: