kops edit

kops edit

Edit clusters and other resources.

Synopsis

Edit a resource configuration. This command changes the desired configuration in the registry.

To set your preferred editor, you can define the EDITOR environment variable. When you have done this, kops will use the editor that you have set.

kops edit does not update the cloud resources, to apply the changes use "kops update cluster".

Examples

  1. # Edit a cluster configuration.
  2. kops edit cluster k8s-cluster.example.com --state=s3://kops-state-1234
  3.  
  4. # Edit a instance group configuration.
  5. kops edit ig --name k8s-cluster.example.com \
  6. --state=s3://kops-state-1234 nodes

Options

  1. -h, --help help for edit

Options inherited from parent commands

  1. --add_dir_header If true, adds the file directory to the header
  2. --alsologtostderr log to standard error as well as files
  3. --config string yaml config file (default is $HOME/.kops.yaml)
  4. --log_backtrace_at traceLocation when logging hits line file:N, emit a stack trace (default :0)
  5. --log_dir string If non-empty, write log files in this directory
  6. --log_file string If non-empty, use this log file
  7. --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)
  8. --logtostderr log to standard error instead of files (default true)
  9. --name string Name of cluster. Overrides KOPS_CLUSTER_NAME environment variable
  10. --skip_headers If true, avoid header prefixes in the log messages
  11. --skip_log_headers If true, avoid headers when opening log files
  12. --state string Location of state storage (kops 'config' file). Overrides KOPS_STATE_STORE environment variable
  13. --stderrthreshold severity logs at or above this threshold go to stderr (default 2)
  14. -v, --v Level number for the log level verbosity
  15. --vmodule moduleSpec comma-separated list of pattern=N settings for file-filtered logging

SEE ALSO