Skip to content

kcp crd snapshot

kcp crd snapshot -f FILE --prefix PREFIX [flags]

Examples

    # Convert a CRD in a yaml file to an APIResourceSchema. For a CRD named widgets.example.io, and a prefix value of
    # 'today', the new APIResourceSchema's name will be today.widgets.example.io.
    kubectl kcp crd snapshot -f crd.yaml --prefix 2022-05-07 > api-resource-schema.yaml

    # Convert a CRD from STDIN
    kubectl get crd foo -o yaml | kubectl kcp crd snapshot -f - --prefix today > output.yaml

Options

  -f, --filename string   Path to a file containing the CRD to convert to an APIResourceSchema, or - for stdin
  -h, --help              help for snapshot
  -o, --output string     Output format. Valid values are 'json' and 'yaml' (default "yaml")
      --prefix string     Prefix to use for the APIResourceSchema's name, before <resource>.<group>

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)
      --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=false) (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