Samuel

Using your new values, I could not reproduce the issue. The deployment object generated is valid and can be applied, kubectl doesn't complain: ```yml --- # Source: traefik/templates/deployment.yaml apiVersion: apps/v1...

I'm not sure this is directly related to Traefik Helm Charts. You probably should ask over there: https://github.com/traefik/traefik/issues As a general observation, using passthrough routes, Traefik is not in charge...

I'm not sure I get it ... are you trying to set a QoS Class into traefik podTemplate? And you've had an outage? The docs you point out to explains...

I'm not sure what could be on. I would check on Traefik pods logs, make sure the client queries are properly redirected to traefik, check the .status field of Ingresses...

Hi, This is supposed to check for the Traefik image/version IngressClasses support. Could you give us a sample of the image tag that would be used in your case? Any...

The configuration of a NetworkPolicy allowing traffic to ingress controllers would depend on your SDN (if using NodePorts/LoadBalancer services, Calico would NAT with network addresses matching host subnets, OVS with...

> Other pods in the namespace that are not selected by any NetworkPolicy will continue to accept all traffic. I'ld have to check. I've been using them for a while...

Indeed. Although if you were to add that `fallbackApiVersion: ""` into your values file, you would still not enter that elsif clause currently causing an error. Only to end up...

FYI, PR was merged yesterday. Can you confirm it solved your issue, @mylesagray ?

You could ignore errors: ``` initContainers: - name: volume-permissions image: busybox:1.35.0 command: ["sh", "-c", "chmod -Rv 600 /data/* || echo oops"] volumeMounts: - name: data mountPath: /data ``` You could...