Logs directory not created in the k9s config/home dir 0.30.1

[den-is]

Removed old k9s directory, and started 0.30.1 clean.
I have different k9s config dirs per global projects, in addition to standard k9s. (each has 1+many k8s clusters).

Checking k9s info shows weird path for logs, for the custom k9s config.

• Custom k9s configuration setup

Version:           0.30.1
Config:            /Users/den/work/xxx/.k9s/config.yaml
Custom Views:      /Users/den/work/xxx/.k9s/views.yaml
Plugins:           /Users/den/work/xxx/.k9s/plugins.yaml
Hotkeys:           /Users/den/work/xxx/.k9s/hotkeys.yaml
Aliases:           /Users/den/work/xxx/.k9s/aliases.yaml
Skins:             /Users/den/work/xxx/.k9s/skins
Context Configs:   /Users/den/work/xxx/.k9s/clusters
Logs:              /var/folders/s_/3qhsp0vs4z14ht8rc_d7087w0000gn/T/k9s/den/k9s.log
Benchmarks:        /Users/den/work/xxx/.k9s/benchmarks
ScreenDumps:       /Users/den/work/xxx/.k9s/screen-dumps

• Default k9s setup

Version:           0.30.1
Config:            /Users/den/Library/Application Support/k9s/config.yaml
Custom Views:      /Users/den/Library/Application Support/k9s/views.yaml
Plugins:           /Users/den/Library/Application Support/k9s/plugins.yaml
Hotkeys:           /Users/den/Library/Application Support/k9s/hotkeys.yaml
Aliases:           /Users/den/Library/Application Support/k9s/aliases.yaml
Skins:             /Users/den/Library/Application Support/k9s/skins
Context Configs:   /Users/den/Library/Application Support/k9s/clusters
Logs:              /Users/den/Library/Application Support/k9s/k9s.log
Benchmarks:        /Users/den/Library/Application Support/k9s/benchmarks
ScreenDumps:       /Users/den/Library/Application Support/k9s/screen-dumps

[derailed]

@den-is K9s logs should go to the user's tmp dir and not in the custom k9s home dir.

[nikaro]

On a shared linux machine it causes some issue. Is there a way to customize this path?

We have a bastion where k9s is installed, and the first user that use the k9s command creates the /tmp/k9s with itself as owner. Thus next users cannot runk9s command because it cannot create their own logs directory.

[den-is]

On a shared linux machine it causes some issue. Is there a way to customize this path?

We have a bastion where k9s is installed, and the first user that use the k9s command creates the /tmp/k9s with itself as owner. Thus next users cannot runk9s command because it cannot create their own logs directory.

"No! ... Suffer and Struggle ... Uncles from outside will tell you, and make you use what they want and how they want it"