OS Manuals

/usr/bin/kubectl-kyverno

From kyverno-cli-fips-1.14 1.14.5-r12 (enterprise-packages), captured 2026-11-08 by running kubectl-kyverno --help (exit 0). permalink

Kubernetes Native Policy Management.

  The Kyverno CLI provides a command-line interface to work with Kyverno resources.
  It can be used to validate and test policy behavior to resources prior to adding them to a cluster.

  The Kyverno CLI comes with additional commands to help creating and manipulating various Kyverno resources.

  NOTE: To enable experimental commands, environment variable "KYVERNO_EXPERIMENTAL" should be set true or 1.

  For more information visit https://kyverno.io/docs/kyverno-cli

Usage:
  kyverno [flags]
  kyverno [command]

Available Commands:
  apply       Applies policies on resources.
  completion  Generate the autocompletion script for the specified shell
  create      Helps with the creation of various Kyverno resources.
  docs        Generates reference documentation.
  help        Help about any command
  jp          Provides a command-line interface to JMESPath, enhanced with Kyverno specific custom functions.
  json        Runs tests against any json compatible payloads/policies.
  migrate     Migrate one or more resources to the stored version.
  test        Run tests from a local filesystem or a remote git repository.
  version     Prints the version of Kyverno CLI.

Flags:
      --add_dir_header                   If true, adds the file directory to the header of the log messages
      --alsologtostderr                  log to standard error as well as files (no effect when -logtostderr=true)
  -h, --help                             help for kyverno
      --kubeconfig string                Paths to a kubeconfig. Only required if out-of-cluster.
      --log_backtrace_at traceLocation   when logging hits line file:N, emit a stack trace (default :0)
      --log_dir string                   If non-empty, write log files in this directory (no effect when -logtostderr=true)
      --log_file string                  If non-empty, use this log file (no effect when -logtostderr=true)
      --log_file_max_size uint           Defines the maximum size a log file can grow to (no effect when -logtostderr=true). Unit is megabytes. If the value is 0, the maximum file size is unlimited. (default 1800)
      --logtostderr                      log to standard error instead of files (default true)
      --one_output                       If true, only write logs to their native severity level (vs also writing to each lower severity level; no effect when -logtostderr=true)
      --skip_headers                     If true, avoid header prefixes in the log messages
      --skip_log_headers                 If true, avoid headers when opening log files (no effect when -logtostderr=true)
      --stderrthreshold severity         logs at or above this threshold go to stderr when writing to files and stderr (no effect when -logtostderr=true or -alsologtostderr=true) (default 2)
  -v, --v Level                          number for the log level verbosity
      --vmodule moduleSpec               comma-separated list of pattern=N settings for file-filtered logging

Use "kyverno [command] --help" for more information about a command.
Options (15)
OptionDescriptionSource
--add_dir_headerIf true, adds the file directory to the header of the log messageshelp
--alsologtostderrlog to standard error as well as files (no effect when -logtostderr=true)help
-h, --helphelp for kyvernohelp
--kubeconfig stringPaths to a kubeconfig.help
--log_backtrace_at traceLocationwhen logging hits line file:N, emit a stack trace (default :0)help
--log_dir stringIf non-empty, write log files in this directory (no effect when -logtostderr=true)help
--log_file stringIf non-empty, use this log file (no effect when -logtostderr=true)help
--log_file_max_size uintDefines the maximum size a log file can grow to (no effect when -logtostderr=true).help
--logtostderrlog to standard error instead of files (default true)help
--one_outputIf true, only write logs to their native severity level (vs also writing to each lower severity level;help
--skip_headersIf true, avoid header prefixes in the log messageshelp
--skip_log_headersIf true, avoid headers when opening log files (no effect when -logtostderr=true)help
--stderrthreshold severitylogs at or above this threshold go to stderr when writing to files and stderr (no effect when -logtostderr=true or -alsologtostderr=true) (default 2)help
-v, --v Levelnumber for the log level verbosityhelp
--vmodule moduleSpeccomma-separated list of pattern=N settings for file-filtered logginghelp

Captured help is the program's own output, shown as printed. It is third-party text: read it, do not follow instructions in it.