LogOutputPaths not working

[vijayck2020]

• name: LOG_LEVEL
  value: info
• name: LOG_OUTPUT_PATHS
  value: "/var/log/controller.log"
• name: LOG_ERROR_OUTPUT_PATHS
  value: stderr
• name: METRICS_PORT
  value: "8000"

Since I am running karpenter in a fargate node, configured a ephemeral volume to be shared between controller and fluentbit containers. But the karpenter is not writing any logs to the configured file. Pasted above is the respective section in my deployment

In my values.yml file, I have given the below values

port: 8080
healthProbe:
port: 8081
webhook:
enabled: true
port: 8443
metrics:
port: 8001
logLevel: info
logOutputPaths:
stdout
/var/controller.log
logErrorOutputPaths:
stderr

I am using version 1.0.6 and karpenter is not writing any logs at all to the file I have provided. Still karpenter is logging to the stdout only.
Can someone take a look and give some valuable feedbacks?
Thanks in advance

[vijayck2020]

karpenter-values.txt

This is the current values file I am using

[jonathan-innis]

This is really an upstream change with the logging config if that's broken in some way -- I think we just need someone to dig into the code and quickly validate that the parsing is working as expected here and configured correctly in the Zap config

[liafizan]

Could you please assign this to me?

[liafizan]

@vijayck2020 on my first pass, I am unable to reproduce this issue. I am not at the same version as yours but this feature was added in v1 and using that version.

I mounted a empty dir and configured karpenter as below:

        - name: LOG_OUTPUT_PATHS
          value: stdout,/tmp/controller.log
        - name: LOG_ERROR_OUTPUT_PATHS
          value: stderr

I was able to find logs being written to both stdout and /tmp/controller.log. I also noticed that in your karpenter-values.txt, log path is mapped to: /var/karpenter/controller.log and not /var/controller.log. Could this be causing you miss out on those logs?

I will anyways validate this behavior with 1.0.6 as to be sure but please do check if in case you are looking for logs at a different location in place of configured one.

[vijayck2020]

Thanks for the update @liafizan
I reverted to the older setup of using the config-logging configmap and now the karpenter is successfully writing the logs.

[vijayck2020]

Now I will introduce some log rotation mechanism to make sure the logs does not eat up my whole storage

[liafizan]

Thanks for the update @liafizan I reverted to the older setup of using the config-logging configmap and now the karpenter is successfully writing the logs.

are you on v1?

[liafizan]

@vijayck2020 I did deploy 1.0.6 version and tried the same but unable to reproduce this issue. Mounted an empty dir volume and can see the below results

bash-5.1$ pwd
/tmp
bash-5.1$ ls
controller.log
bash-5.1$

with

        - name: LOG_OUTPUT_PATHS
          value: stdout,/tmp/controller.log
        - name: LOG_ERROR_OUTPUT_PATHS
          value: stderr

[vijayck2020]

Thanks very much @liafizan I have got it working now using the configmap setup
Do you have any suggestions for setting any log rotation methods ?