You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ArgoCD (argocd-dex) starts dex with a YAML configuration from argocd_dex.go#L100. Before starting dex, it parses cli arguments logformat and loglevel :
What is the problem
ArgoCD (argocd-dex) starts
dex
with a YAML configuration from argocd_dex.go#L100. Before starting dex, it parses cli argumentslogformat
andloglevel
:argo-cd/cmd/argocd-dex/commands/argocd_dex.go
Lines 139 to 140 in bc4c475
into cmd/util
argo-cd/cmd/util/common.go
Lines 3 to 6 in bc4c475
However, the dex YAML configuration parses environment variables defined in
common
anew (ARGOCD_LOG_LEVEL
,ARGOCD_LOG_FORMAT
):argo-cd/util/dex/config.go
Lines 52 to 55 in bc4c475
These sets of arguments/variables are misaligned.
What we observe
Our deployment YAML contains:
We expected this would log everything as json, and at info level. However, the logs contain the following:
This contains non-json logs on the stderr stream, resulting in non-errors reported as errors.
The text was updated successfully, but these errors were encountered: