completion

Generate command completion for a shell

minikube completion

Generate command completion for a shell

Synopsis

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

  1. This depends on the bash-completion binary. Example installation instructions:
  2. OS X:
  3. $ brew install bash-completion
  4. $ source $(brew --prefix)/etc/bash_completion
  5. $ minikube completion bash > ~/.minikube-completion # for bash users
  6. $ minikube completion zsh > ~/.minikube-completion # for zsh users
  7. $ source ~/.minikube-completion
  8. $ minikube completion fish > ~/.config/fish/completions/minikube.fish # for fish users
  9. Ubuntu:
  10. $ apt-get install bash-completion
  11. $ source /etc/bash_completion
  12. $ source <(minikube completion bash) # for bash users
  13. $ source <(minikube completion zsh) # for zsh users
  14. $ minikube completion fish > ~/.config/fish/completions/minikube.fish # for fish users
  15. Additionally, you may want to output the completion to a file and source in your .bashrc
  16. Note for zsh users: [1] zsh completions are only supported in versions of zsh >= 5.2
  17. Note for fish users: [2] please refer to this docs for more details https://fishshell.com/docs/current/#tab-completion
  1. minikube completion SHELL [flags]

Options inherited from parent commands

  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. -b, --bootstrapper string The name of the cluster bootstrapper that will set up the Kubernetes cluster. (default "kubeadm")
  4. -h, --help
  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
  10. --one_output If true, only write logs to their native severity level (vs also writing to each lower severity level)
  11. -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")
  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. --stderrthreshold severity logs at or above this threshold go to stderr (default 2)
  15. --user string Specifies the user executing the operation. Useful for auditing operations executed by 3rd party tools. Defaults to the operating system username.
  16. -v, --v Level number for the log level verbosity
  17. --vmodule moduleSpec comma-separated list of pattern=N settings for file-filtered logging

minikube completion bash

bash completion.

Synopsis

Generate command completion for bash.

  1. minikube completion bash [flags]

Options inherited from parent commands

  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. -b, --bootstrapper string The name of the cluster bootstrapper that will set up the Kubernetes cluster. (default "kubeadm")
  4. -h, --help
  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
  10. --one_output If true, only write logs to their native severity level (vs also writing to each lower severity level)
  11. -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")
  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. --stderrthreshold severity logs at or above this threshold go to stderr (default 2)
  15. --user string Specifies the user executing the operation. Useful for auditing operations executed by 3rd party tools. Defaults to the operating system username.
  16. -v, --v Level number for the log level verbosity
  17. --vmodule moduleSpec comma-separated list of pattern=N settings for file-filtered logging

minikube completion fish

fish completion.

Synopsis

Generate command completion for fish .

  1. minikube completion fish [flags]

Options inherited from parent commands

  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. -b, --bootstrapper string The name of the cluster bootstrapper that will set up the Kubernetes cluster. (default "kubeadm")
  4. -h, --help
  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
  10. --one_output If true, only write logs to their native severity level (vs also writing to each lower severity level)
  11. -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")
  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. --stderrthreshold severity logs at or above this threshold go to stderr (default 2)
  15. --user string Specifies the user executing the operation. Useful for auditing operations executed by 3rd party tools. Defaults to the operating system username.
  16. -v, --v Level number for the log level verbosity
  17. --vmodule moduleSpec comma-separated list of pattern=N settings for file-filtered logging

minikube completion help

Help about any command

Synopsis

Help provides help for any command in the application. Simply type completion help [path to command] for full details.

  1. minikube completion help [command] [flags]

Options inherited from parent commands

  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. -b, --bootstrapper string The name of the cluster bootstrapper that will set up the Kubernetes cluster. (default "kubeadm")
  4. -h, --help
  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
  10. --one_output If true, only write logs to their native severity level (vs also writing to each lower severity level)
  11. -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")
  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. --stderrthreshold severity logs at or above this threshold go to stderr (default 2)
  15. --user string Specifies the user executing the operation. Useful for auditing operations executed by 3rd party tools. Defaults to the operating system username.
  16. -v, --v Level number for the log level verbosity
  17. --vmodule moduleSpec comma-separated list of pattern=N settings for file-filtered logging

minikube completion zsh

zsh completion.

Synopsis

Generate command completion for zsh.

  1. minikube completion zsh [flags]

Options inherited from parent commands

  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. -b, --bootstrapper string The name of the cluster bootstrapper that will set up the Kubernetes cluster. (default "kubeadm")
  4. -h, --help
  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
  10. --one_output If true, only write logs to their native severity level (vs also writing to each lower severity level)
  11. -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")
  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. --stderrthreshold severity logs at or above this threshold go to stderr (default 2)
  15. --user string Specifies the user executing the operation. Useful for auditing operations executed by 3rd party tools. Defaults to the operating system username.
  16. -v, --v Level number for the log level verbosity
  17. --vmodule moduleSpec comma-separated list of pattern=N settings for file-filtered logging

Last modified April 25, 2021: make generate-docs (0e228aa4e)