César Sepúlveda

Ok i found something. I modified the Probe Period to 300s and the cpu usage goes from 250m-300m to 20m-30m Why this probe take so much CPU? there is another...

Stats after change the scheduler.livenessProbe.periodSeconds to 300 

I got the same issue: If i disable the option `focus follow mouse` the issue its solved.

Same issue here: ``` 2023-09-20T18:00:24.128Z DEBUG boringtun::noise::timers: KEEPALIVE(PERSISTENT_KEEPALIVE) 2023-09-20T18:00:48.298Z DEBUG boringtun::noise::timers: KEEPALIVE(PERSISTENT_KEEPALIVE) 2023-09-20T18:01:12.487Z DEBUG boringtun::noise::timers: KEEPALIVE(PERSISTENT_KEEPALIVE) 2023-09-20T18:01:36.691Z DEBUG boringtun::noise::timers: KEEPALIVE(PERSISTENT_KEEPALIVE) 2023-09-20T18:02:00.870Z DEBUG boringtun::noise::timers: KEEPALIVE(PERSISTENT_KEEPALIVE) 2023-09-20T18:02:25.090Z DEBUG boringtun::noise::timers: KEEPALIVE(PERSISTENT_KEEPALIVE) 2023-09-20T18:02:35.978Z DEBUG...

Let me explain a little bit more. When i make a request to the application behind nginx, if the request have to be authorized using auth-url, the opentracing headers (w3s)...

Maybe its necessary to force the header using something like: ``` nginx.ingress.kubernetes.io/auth-url: http://foo.com/external-auth nginx.ingress.kubernetes.io/auth-snippet: | proxy_set_header traceparent $traceparent; ``` Is there a way to get the traceparent as a variable?

I tried the following configuration: ``` nginx.ingress.kubernetes.io/auth-snippet: | proxy_set_header traceparent 123; ``` and i'm able to see the header on the authorized service: ``` ... X-Auth-Request-Redirect: /v2/offers. traceparent: 123. Connection:...

Here is an example to reproduce the issue: https://github.com/csepulveda/nginx-example The expected result is to see the service-c span inside the trace generated by Nginx. Regards!

+1, waiting this :)

Hello @esigo, do you know when this could be merged and released? Regards!!!