K9S opt-out mechanisms give you that control. They let you disable, skip, or silence parts of the K9S interface you don’t need. The result is a faster, cleaner workflow inside your Kubernetes clusters.
K9S loads plugins, views, and telemetry by default. These defaults are helpful for many, but not for all. Opt-out paths let you strip K9S down to the essentials. When cluster complexity grows, removing distractions is an edge you can measure.
Configuring K9S Opt-Out Mechanisms
All opt-out controls start in the k9s.yml config file. You can define them globally or per context. Common opt-out cases include:
- Disabling plugins: Comment out or remove plugin configs in
plugins.ymlto stop extra scripts from loading on every session. - Turning off telemetry: In
k9s.yml, setdisablePodCounters: trueor similar keys to reduce background metrics collection. - Hiding views: Use
views: disabled: [“<view_name>”]to keep unused resource views from appearing in the navigation. - Muting logs and events: Set
logLevel: offwhere possible to stop verbose outputs that slow you down.
Environment Variable Overrides
K9S supports opt-out via environment variables for runtime changes without editing config files. For example, unset K9S_PLUGIN_DIR to prevent plugin discovery, or set flags like K9S_DISABLE_METRICS=true to skip metric polling.