Octant is configurable through environment variables defined at runtime, here are some of the notable variables:
KUBECONFIG- set to non-empty location if you want to set KUBECONFIG with an environment variable.
OCTANT_NAMESPACE- initial namespace to load when Octant starts.
OCTANT_CONTEXT- intial context to load when Octant starts.
OCTANT_DISABLE_CLUSTER_OVERVIEW- disable cluster overview when a context does not have cluster level permissions.
OCTANT_PLUGIN_PATH- add a plugin directory or multiple directories separated by
:. Plugins will load by default from
Notice: If using fish shell, tilde expansion may not occur when using
env to set environment variables.
All command-line flags can also be passed as environment variables by using all UPPERCASE, replacing the
_ and prefixing them with
When using CLI flags that enable/disable a feature the following values are considered true and false:
Octant is configurable through command line flags set at runtime. You can see all of the available options by
The verbosity has a special type that is used to parse the flag, which means it can be provided
shorthand by just adding more
v to equal the level count or with an explicit equal sign.
-v[vv], --verbosity=count verbosity level
Is equal to