Open cer opened 1 year ago
hello @cer, could you please post the versions of Flagger and Linkerd you're running? thanks
@aryan9600 i think he is running https://github.com/stefanprodan/gitops-linkerd which uses latest charts
@aryan9600 i think he is running https://github.com/stefanprodan/gitops-linkerd which uses latest charts
Yes.
The underlying problem was that Flagger was missing: linkerdAuthPolicy.create=true
, which resulted in HTTP 403s:
kubectl logs -n linkerd-viz prometheus-5cbbbcd594-7lsvn -f
[ 46648.721175s] INFO ThreadId(01) inbound:server{port=9090}: linkerd_app_inbound::policy::http: Request denied server.group=policy.linkerd.io server.kind=server server.name=prometheus-admin route.group= route.kind=default route.name=default client.tls=None(NoClientHello) client.ip=10.244.0.62
@cer yes linkerdAuthPolicy.create=true
is required for Linkerd >= 2.13, as an AuthorizationPolicy
is now needed to access the prom server running in the linkerd-viz
ns, see: https://github.com/fluxcd/flagger/blob/main/CHANGELOG.md#1310
we could also include the status code in the error message? @stefanprodan
I'm trying: https://docs.flagger.app/tutorials/linkerd-progressive-delivery
When I describe the canary deployment - which ultimately failed - I see the following:
The first warning has a typo and was most likely caused by delays during starting pods.
The second warning occurred during the canary rollout which failed. It's unclear what the problem is.
I successfully executed these queries in the Prometheus console so the data is present.