kops

kops

kOps is Kubernetes Operations.

Synopsis

kOps is Kubernetes Operations.

kOps is the easiest way to get a production grade Kubernetes cluster up and running. We like to think of it as kubectl for clusters.

kOps helps you create, destroy, upgrade and maintain production-grade, highly available, Kubernetes clusters from the command line. AWS (Amazon Web Services) is currently officially supported, with Digital Ocean and OpenStack in beta support.

Options

  1. --add_dir_header If true, adds the file directory to the header of the log messages
  2. --alsologtostderr log to standard error as well as files
  3. --config string yaml config file (default is $HOME/.kops.yaml)
  4. -h, --help help for kops
  5. --log_backtrace_at traceLocation when logging hits line file:N, emit a stack trace (default :0)
  6. --log_dir string If non-empty, write log files in this directory
  7. --log_file string If non-empty, use this log file
  8. --log_file_max_size uint Defines the maximum size a log file can grow to. Unit is megabytes. If the value is 0, the maximum file size is unlimited. (default 1800)
  9. --logtostderr log to standard error instead of files (default true)
  10. --name string Name of cluster. Overrides KOPS_CLUSTER_NAME environment variable
  11. --one_output If true, only write logs to their native severity level (vs also writing to each lower severity level)
  12. --skip_headers If true, avoid header prefixes in the log messages
  13. --skip_log_headers If true, avoid headers when opening log files
  14. --state string Location of state storage (kops 'config' file). Overrides KOPS_STATE_STORE environment variable
  15. --stderrthreshold severity logs at or above this threshold go to stderr (default 2)
  16. -v, --v Level number for the log level verbosity
  17. --vmodule moduleSpec comma-separated list of pattern=N settings for file-filtered logging

SEE ALSO