Smaine Kahlouch

The patch from @damienleger works great. thanks

Hi @kolbe , actually we're facing the same problem using the `tidb-initializer` resource: When we run the job it uses a mysql client and returns the following error: ``` Traceback...

Ok thanks for the tip @tohojo. I'll get back to you if I get an answer

> @Smana just checking if you managed to get an answer from any of the maintainers on native XDP support in bnx2x No I didn't. It's been a long time...

By the way, I've updated the CRD manually but there may be a way to automatically generate it. Please let me know

Generally speaking that would be useful to update the ingress annotations. In our case we make use of many nginx ingress configuration items such as: ``` apiVersion: extensions/v1beta1 kind: Ingress...

Same issue with `kubectl rollout status ...`

same for `ingresses` deletion

Well I tested several values and nothing worked so far. Here are the info about the environment: kubectl: tested with `1.17.17` and `1.20.4` kubernetes: 1.17.17 image: `quay.io/jetstack/kube-oidc-proxy:v0.3.0` kube-oidc-proxy flags: ```yaml...

Still digging because I face the issue when I enable the audit logs. ```yaml - --audit-log-path=- - --audit-policy-file=/etc/oidc/audit/audit-policy.yaml ```