Azure / Azure/ip-masq-agent-v2
How can I set log level or reduce logs verbosity?
- Dominant language
- Go
- Stars
- 14
- Forks
- 24
- PR merge metrics
- No merged PRs in 30d
Description
Hello,
I'm running an aks cluster (with kubernetes v1.23.5) and I'd like to limit the logs generated by ip-masq-agent-v2 to errors. I've seen that I could use the -v flag and set it to 1 in the daemonset for example, but somehow the default value 2 is always restored.
That's what I'm doing:
`kubectl edit daemonset azure-ip-masq-agent -n kube-system`
replace `- --v=2` by `- --v=1`
save and exit
pods are recreated and it looks good, but a few minutes later, logs are coming again.
If I redo `kubectl edit daemonset azure-ip-masq-agent -n kube-system`, I can see the that -v is set to 2 again.
Do you have any idea of what I can do there?
Thanks
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the azure-ip-masq-agent DaemonSet in the kube-system namespace and reproduce the change using kubectl edit, focusing on why -v=1 is replaced by -v=2 after pods are recreated. Done means identifying the component that restores the argument and confirming that the configured log level remains effective without recurring verbosity.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100