aatarasoff / linkerd-easyauth Goto Github PK

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:

1. 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
2. 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

We still need to use caching to make command response fast on the scale

We've removed obsolete healthcheck ServerAuthorization resource but it is useful to have common NetworkAuthentication to attach it to healthcheck HTTPRoutess in case of using per-route policies

What do we want:

• take account of HTTPRoutes while checking authorizations
• check that all HTTPRoutes still have targetRef

The resources can be created but not attached to any policy so we need to check that in authcheck command