Installing Linux using Virtual Machine This is a popular method to install a Linux operating system. The virtual installation offers you the freedom of running Linux on an existing OS already installed on your computer. This means if you have Windows running, then you can just run Linux with a click of a button. Installation on Linux Download the latest Linux version of Acunetix from the download location provided. Open a Terminal Windows. Use chmod to add executable permissions on the installation file E.g. Run the installation. In case there are.

The Kubernetes command-line tool, kubectl, allows you to run commands against Kubernetes clusters. You can use kubectl to deploy applications, inspect and manage cluster resources, and view logs. For a complete list of kubectl operations, see Overview of kubectl.

Before you begin

You must use a kubectl version that is within one minor version difference of your cluster. For example, a v1.2 client should work with v1.1, v1.2, and v1.3 master. Using the latest version of kubectl helps avoid unforeseen issues.

Install kubectl on Linux

Install kubectl binary with curl on Linux

1. Download the latest release with the command:

   To download a specific version, replace the $(curl -s https://storage.googleapis.com/kubernetes-release/release/stable.txt) portion of the command with the specific version.

   For example, to download version v1.17.0 on Linux, type:

2. Make the kubectl binary executable.

3. Move the binary in to your PATH.

4. Test to ensure the version you installed is up-to-date:

Install using native package management

Install using other package management

If you are on Ubuntu or another Linux distribution that support snap package manager, kubectl is available as a snap application.

If you are on Linux and using Homebrew package manager, kubectl is available for installation.

Fallout 4 adoption mod. Mon, Sep 18th 2017 4:01pm —You may recall that a few years ago, Valve attempted to rollout a platform for video game to make money from their efforts.

Install kubectl on macOS

Install kubectl binary with curl on macOS

1. Download the latest release:

   To download a specific version, replace the $(curl -s https://storage.googleapis.com/kubernetes-release/release/stable.txt) portion of the command with the specific version.

   For example, to download version v1.17.0 on macOS, type:

2. Make the kubectl binary executable.

3. Move the binary in to your PATH.

4. Test to ensure the version you installed is up-to-date:

Install with Homebrew on macOS

If you are on macOS and using Homebrew package manager, you can install kubectl with Homebrew.

1. Run the installation command:

   or

2. Test to ensure the version you installed is up-to-date:

Install with Macports on macOS

If you are on macOS and using Macports package manager, you can install kubectl with Macports.

1. Run the installation command:

2. Test to ensure the version you installed is up-to-date:

Install kubectl on Windows

Install kubectl binary with curl on Windows

1. Download the latest release v1.17.0 from this link.

   Or if you have curl installed, use this command:

   To find out the latest stable version (for example, for scripting), take a look at https://storage.googleapis.com/kubernetes-release/release/stable.txt.

2. Add the binary in to your PATH.

3. Test to ensure the version of kubectl is the same as downloaded:

Install with Powershell from PSGallery

If you are on Windows and using Powershell Gallery package manager, you can install and update kubectl with Powershell.

1. Run the installation commands (making sure to specify a DownloadLocation):

   Note: If you do not specify a DownloadLocation, kubectl will be installed in the user’s temp Directory.

   The installer creates $HOME/.kube and instructs it to create a config file

2. Test to ensure the version you installed is up-to-date:

   Note: Updating the installation is performed by rerunning the two commands listed in step 1.

Install on Windows using Chocolatey or Scoop

To install kubectl on Windows you can use either Chocolatey package manager or Scoop command-line installer.

1. Test to ensure the version you installed is up-to-date:

2. Navigate to your home directory:

3. Create the .kube directory:

4. Change to the .kube directory you just created:

5. Configure kubectl to use a remote Kubernetes cluster:

   Note: Edit the config file with a text editor of your choice, such as Notepad.

Download as part of the Google Cloud SDK

You can install kubectl as part of the Google Cloud SDK.

1. Install the Google Cloud SDK.

2. Run the kubectl installation command:

3. Test to ensure the version you installed is up-to-date:

Verifying kubectl configuration

In order for kubectl to find and access a Kubernetes cluster, it needs a kubeconfig file, which is created automatically when you create a cluster using kube-up.sh or successfully deploy a Minikube cluster. By default, kubectl configuration is located at ~/.kube/config.

Check that kubectl is properly configured by getting the cluster state:

If you see a URL response, kubectl is correctly configured to access your cluster.

If you see a message similar to the following, kubectl is not configured correctly or is not able to connect to a Kubernetes cluster.

For example, if you are intending to run a Kubernetes cluster on your laptop (locally), you will need a tool like Minikube to be installed first and then re-run the commands stated above.

If kubectl cluster-info returns the url response but you can’t access your cluster, to check whether it is configured properly, use:

Optional kubectl configurations

Enabling shell autocompletion

kubectl provides autocompletion support for Bash and Zsh, which can save you a lot of typing.

Below are the procedures to set up autocompletion for Bash (including the difference between Linux and macOS) and Zsh.

Introduction

The kubectl completion script for Bash can be generated with the command kubectl completion bash. Sourcing the completion script in your shell enables kubectl autocompletion.

However, the completion script depends on bash-completion, which means that you have to install this software first (you can test if you have bash-completion already installed by running type _init_completion).

Install bash-completion

bash-completion is provided by many package managers (see here). You can install it with apt-get install bash-completion or yum install bash-completion, etc.

The above commands create /usr/share/bash-completion/bash_completion, which is the main script of bash-completion. Depending on your package manager, you have to manually source this file in your ~/.bashrc file.

To find out, reload your shell and run type _init_completion. If the command succeeds, you’re already set, otherwise add the following to your ~/.bashrc file:

Reload your shell and verify that bash-completion is correctly installed by typing type _init_completion.

Enable kubectl autocompletion

You now need to ensure that the kubectl completion script gets sourced in all your shell sessions. There are two ways in which you can do this:

• Source the completion script in your ~/.bashrc file:

• Add the completion script to the /etc/bash_completion.d directory:

• If you have an alias for kubectl, you can extend shell completion to work with that alias:

Both approaches are equivalent. After reloading your shell, kubectl autocompletion should be working.

Introduction

The kubectl completion script for Bash can be generated with kubectl completion bash. Sourcing this script in your shell enables kubectl completion.

However, the kubectl completion script depends on bash-completion which you thus have to previously install.

Install bash-completion

You can test if you have bash-completion v2 already installed with type _init_completion. If not, you can install it with Homebrew:

As stated in the output of this command, add the following to your ~/.bashrc file:

Reload your shell and verify that bash-completion v2 is correctly installed with type _init_completion.

Enable kubectl autocompletion

You now have to ensure that the kubectl completion script gets sourced in all your shell sessions. There are multiple ways to achieve this:

• Source the completion script in your ~/.bashrc file:

• Add the completion script to the /usr/local/etc/bash_completion.d directory:

• If you have an alias for kubectl, you can extend shell completion to work with that alias:

• If you installed kubectl with Homebrew (as explained above), then the kubectl completion script should already be in /usr/local/etc/bash_completion.d/kubectl. In that case, you don’t need to do anything.

In any case, after reloading your shell, kubectl completion should be working.

The kubectl completion script for Zsh can be generated with the command kubectl completion zsh. Sourcing the completion script in your shell enables kubectl autocompletion.

To do so in all your shell sessions, add the following to your ~/.zshrc file:

If you have an alias for kubectl, you can extend shell completion to work with that alias:

After reloading your shell, kubectl autocompletion should be working.

If you get an error like complete:13: command not found: compdef, then add the following to the beginning of your ~/.zshrc file:

What's next

• See the getting started guides for more about creating clusters.
• If you need access to a cluster you didn’t create, see the Sharing Cluster Access document.
• Read the kubectl reference docs

Feedback

Was this page helpful?

Thanks for the feedback. If you have a specific, answerable question about how to use Kubernetes, ask it onStack Overflow.Open an issue in the GitHub repo if you want toreport a problemorsuggest an improvement.