Versions Impacted: DKP 2.5.0, DKP 2.5.1
There is currently a known issue in DKP 2.5 where traefik-forward-auth-mgmt has the `LOG_LEVEL` environment variable set twice:
There is currently a known issue in DKP 2.5 where traefik-forward-auth-mgmt has the `LOG_LEVEL` environment variable set twice:
spec:
containers:
- args:
- --enable-impersonation
- --enable-rbac
env:
- name: LOG_LEVEL
value: warn
- name: CONFIG
value: /etc/traefik-forward-auth/config/config.ini
- name: SSL_CERT_FILE
value: /etc/traefik-forward-auth/ca/ca.crt
- name: LOG_LEVEL
value: trace
This is due to the value being hardcoded in the Helm chart and set to "trace", while also being set to "warn" in the configmap override. As a result, the value is set to "trace" with no way to reconfigure it.
Until you install a version of the product with a fix, the only way to set the log level to "warn" is to edit the deployment:
kubectl edit deployment traefik-forward-auth-mgmt -n kommander
Remove this section:
- name: LOG_LEVEL
value: trace
Making the change this way will mean that it will not survive upgrades and will be reverted if any other config changes are made to this appdeployment. This problem is corrected in DKP 2.5.2.