**What K9S User Config Dependent Means**
K9S reads from a user-specific configuration file, usually stored in $HOME/.k9s/config.yml. This file is independent of the cluster itself. It controls resource aliases, UI layout, refresh rates, and which contexts load by default. When something seems off in your K9S display, it often traces back to user config dependent logic — behaviors tied to the personal settings, not the cluster state.
Key Factors Controlled by User Config
- Cluster Contexts: Define default and fallback contexts to switch seamlessly.
- Resource Customization: Map aliases, hide unused resources, and tailor output fields.
- UI Behavior: Set refresh intervals, enable or disable crumbs, manage dark mode.
- Plugins: Configure commands and shortcuts directly in the config file.
These settings are loaded at runtime. Any change requires saving the file, then rebooting K9S to see the impact. Because profiles are user config dependent, team members can operate in the same cluster with entirely different views and command sets.