We use analytics and cookies to understand site traffic. Information about your use of our site is shared with Google for that purpose. Learn more.
You can customize your
kn CLI setup by creating a
config.yaml configuration file. You can provide this configuration by using the
--config flag, otherwise the configuration is picked up from a default location. The default configuration location conforms to the XDG Base Directory Specification, and is different for Unix systems and Windows systems.
- If the
XDG_CONFIG_HOMEenvironment variable is set, the default configuration location that
knlooks for is
- If the
XDG_CONFIG_HOMEenvironment variable is not set,
knlooks for the configuration in the home directory of the user at
- For Windows systems, the default
knconfiguration location is
Example configuration file
plugins: path-lookup: true directory: ~/.config/kn/plugins eventing: sink-mappings: - prefix: svc group: core version: v1 resource: services
knshould look for plugins in the
PATHenvironment variable. This is a boolean configuration option. The default value is
directoryspecifies the directory where
knwill look for plugins. The default path depends on the operating system, as described above. This can be any directory that is visible to the user.
sink-mappingsdefines the Kubernetes Addressable resource that is used when you use the
--sinkflag with a
prefix: The prefix you want to use to describe your sink. Service,
brokerare predefined prefixes in
group: The API group of the Kubernetes resource.
version: The version of the Kubernetes resource.
resource: The plural name of the Kubernetes resource type. For example,
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.