Skip to content
This repository has been archived by the owner on Jun 20, 2024. It is now read-only.

Cant Set logLevel for kubernetes Deployment #3342

Closed
tmedford opened this issue Jul 8, 2018 · 4 comments · Fixed by #3683
Closed

Cant Set logLevel for kubernetes Deployment #3342

tmedford opened this issue Jul 8, 2018 · 4 comments · Fixed by #3683

Comments

@tmedford
Copy link

tmedford commented Jul 8, 2018

I may be missing something but I cant see anyway to set the log level of weave-npc or weave via ENV vars for kuberentes deployment.

@bboreham
Copy link
Contributor

bboreham commented Jul 8, 2018

It’s a command-line argument —log-level

Please can you provide more context why you specifically need an environment variable.

@brb
Copy link
Contributor

brb commented Jul 9, 2018

We do not document how to change the log levels at https://www.weave.works/docs/net/latest/kubernetes/kube-addon/.

For weave, you can pass --log-level=... via the EXTRA_ARGS env arg.

@jrryjcksn
Copy link

I'd like to address this, but I want to be completely clear on what's being asked. I followed the link in the comment above but found the following:

By default log level of weave container is set to info level. If you wish to see more detailed logs you can set the desired log level for the -log-level flag through the EXTRA_ARGS environment variable for the weave container in the weave-net daemon set. Add environment variable as below. and an example:

containers:
- command:
- /home/weave/launch.sh
name: weave
env:
- name: EXTRA_ARGS
value: --log-level=debug

The comment says we do not document how to change it. I'm a bit confused. Can someone clarify exactly what needs to be fixed?

@jrryjcksn jrryjcksn removed their assignment Feb 5, 2019
@murali-reddy
Copy link
Contributor

#3391 added the documentation which should have closed this issue. But as you already linked this issue to #3594 with extra details its fine.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants