---
title: karmadactl completion
---

Output shell completion code for the specified shell (bash, zsh, fish)

### Synopsis

Output shell completion code for the specified shell (bash, zsh, fish). The shell code must be evaluated to provide interactive completion of karmadactl commands. This can be done by sourcing it from the .bash_profile.

 Note for zsh users: zsh completions are only supported in versions of zsh >= 5.2.

```
karmadactl completion SHELL
```

### Examples

```
  # Installing bash completion on Linux
  ## If bash-completion is not installed on Linux, install the 'bash-completion' package
  1. apt-get install bash-completion
  2. source /usr/share/bash-completion/bash_completion
  ## Load the karmadactl completion code for bash into the current shell
  source <(karmadactl completion bash)
  ## Or, write bash completion code to a file and source it from .bash_profile
  1. karmadactl completion bash > ~/.kube/completion.bash.inc
  2. echo "source '$HOME/.kube/completion.bash.inc'" >> $HOME/.bash_profile
  3. source $HOME/.bash_profile
  
  # Load the karmadactl completion code for zsh into the current shell
  source <(karmadactl completion zsh)
  # Set the karmadactl completion code for zsh to autoload on startup
  karmadactl completion zsh > "${fpath[1]}/karmadactl"
  
  # Load the karmadactl completion code for fish into the current shell
  karmadactl completion fish | source
  # To load completions for each session, execute once:
  karmadactl completion fish > ~/.config/fish/completions/karmadactl.fish
```

### Options

```
  -h, --help   help for completion
```

### 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)
      --kubeconfig string                Paths to a kubeconfig. Only required if out-of-cluster.
      --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=true) (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

* [karmadactl](karmadactl.md)	 - karmadactl controls a Kubernetes Cluster Federation.

#### Go Back to [Karmadactl Commands](karmadactl_index.md) Homepage.


###### Auto generated by [spf13/cobra script in Karmada](https://github.com/karmada-io/karmada/tree/master/hack/tools/genkarmadactldocs).