kyverno create cluster-role

kyverno create cluster-role

Create an aggregated role for given resource types

Synopsis

This command generates a Kubernetes ClusterRole for specified resource types. The output is printed to stdout by default or saved to a specified file. Required flags include ‘api-groups’, ‘verbs’, and ‘resources’.

kyverno create cluster-role [name]  [flags]

Options

  -g, --api-groups string         API group for the resource (required)
      --controllers stringArray   List of controllers for the ClusterRole (default = background-controller) (default [background-controller])
  -h, --help                      help for cluster-role
  -o, --output string             Output file path (prints to console if not set)
      --resources stringArray     A comma separated list of resources (required)
      --verbs stringArray         A comma separated list of verbs or 'all' for all verbs

Options inherited from parent commands

      --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)
      --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

SEE ALSO

• kyverno create - Helps with the creation of various Kyverno resources.