Generate command completion for a shell

minikube completion

Generate command completion for a shell


Outputs minikube shell completion for the given shell (bash, zsh or fish)

This depends on the bash-completion binary.  Example installation instructions:
    $ brew install bash-completion
    $ source $(brew --prefix)/etc/bash_completion
    $ minikube completion bash > ~/.minikube-completion  # for bash users
    $ minikube completion zsh > ~/.minikube-completion  # for zsh users
    $ source ~/.minikube-completion
    $ minikube completion fish > ~/.config/fish/completions/ # for fish users
    $ apt-get install bash-completion
    $ source /etc/bash-completion
    $ source <(minikube completion bash) # for bash users
    $ source <(minikube completion zsh) # for zsh users
    $ minikube completion fish > ~/.config/fish/completions/ # for fish users

Additionally, you may want to output the completion to a file and source in your .bashrc

Note for zsh users: [1] zsh completions are only supported in versions of zsh >= 5.2
Note for fish users: [2] please refer to this docs for more details
minikube completion SHELL [flags]

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
  -b, --bootstrapper string              The name of the cluster bootstrapper that will set up the Kubernetes cluster. (default "kubeadm")
  -h, --help                             
      --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
      --log_file string                  If non-empty, use this log file
      --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)
      --logtostderr                      log to standard error instead of files
      --one_output                       If true, only write logs to their native severity level (vs also writing to each lower severity level
  -p, --profile string                   The name of the minikube VM being used. This can be set to allow having multiple instances of minikube independently. (default "minikube")
      --skip_headers                     If true, avoid header prefixes in the log messages
      --skip_log_headers                 If true, avoid headers when opening log files
      --stderrthreshold severity         logs at or above this threshold go to stderr (default 2)
      --user string                      Specifies the user executing the operation. Useful for auditing operations executed by 3rd party tools. Defaults to the operating system username.
  -v, --v Level                          number for the log level verbosity
      --vmodule moduleSpec               comma-separated list of pattern=N settings for file-filtered logging