* Refreshing installation instructions (#7495) * Refreshing installation instructions Added conjure-up. Updated displays and juju versions to current versions. * Updated anchors * Fixed image value version typo (#7768) Was inconsistent with other values * Update flocker reference to the github repo (#7784) * Fix typo in federation document (#7779) * an user -> a user (#7778) * Events are namespaced (#7767) * fix 'monitoring' link lose efficacy problem' (#7764) * docs/concepts/policy/pod-security-policy.md: minor fix. (#7659) * Update downward-api-volume-expose-pod-information.md (#7771) * Update downward-api-volume-expose-pod-information.md The pod spec puts the downward api files into /etc/podinfo, not directly in /etc. Updated docs to reflect this fact. * Update downward-api-volume-expose-pod-information.md One more spot needed fixing. * Update downward-api-volume-expose-pod-information.md Yet another fix, in the container example. * Add Amadeus Case Study (#7783) * Add Amadeus Case Study * add Amadeus logo * Fixed Cyrillic с in 'kube-proxy-cm' (#7787) There was a typo (wrong character) in kube-proxy-cm.yaml - Cyrillic с (UTF-8 0x0441) was used instead of Latin c. * install-kubectl: choose one installation method (#7705) The previous text layout suggested that all installations had to be done, one after another. * Update install-kubeadm.md (#7781) Add note to kubeadm install instruction to help install in other arch i.e. aarch64, ppc64le etc. * repair failure link (#7788) * repair failure link * repair failure link * do change as required * Update k8s201.md (#7777) * Update k8s201.md Change instructions to download yams files directly from the website (as used in other pages.) Added instructions to delete labeled pod to avoid warnings in the subsequent deployment step. * Update k8s201.md Added example of using the exposed host from the a node running Kubernetes. (This works on AWS with Weave; not able to test it on other variations...) * Gramatical fix to kompose introduction (#7792) The original wording didn't through very well. As much of the original sentence has been preserved as possible, primarily to ensure the kompose web address is see both in text and as a href link. * update amadeus.html (#7800) * Fix a missing word in endpoint reconciler section (#7804) * add toc entry for pvcprotection downgrade issue doc
8.7 KiB
reviewers, title
| reviewers | title | ||
|---|---|---|---|
|
Install and Set Up kubectl |
{% capture overview %} Use the Kubernetes command-line tool, kubectl, to deploy and manage applications on Kubernetes. Using kubectl, you can inspect cluster resources; create, delete, and update components; and look at your new cluster and bring up example apps. {% endcapture %}
{% capture prerequisites %} Use a version of kubectl that is the same version as your server or later. Using an older kubectl with a newer server might produce validation errors. {% endcapture %}
Install kubectl
Here are a few methods to install kubectl. Pick the one that suits your environment best.
{% capture steps %}
Install kubectl binary via curl
{% capture macos %}
-
Download the latest release with the command:
curl -LO https://storage.googleapis.com/kubernetes-release/release/`curl -s https://storage.googleapis.com/kubernetes-release/release/stable.txt`/bin/darwin/amd64/kubectlTo 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 {{page.fullversion}} on MacOS, type:
curl -LO https://storage.googleapis.com/kubernetes-release/release/{{page.fullversion}}/bin/darwin/amd64/kubectl -
Make the kubectl binary executable.
chmod +x ./kubectl -
Move the binary in to your PATH.
sudo mv ./kubectl /usr/local/bin/kubectl
{% endcapture %}
{% capture linux %}
-
Download the latest release with the command:
curl -LO https://storage.googleapis.com/kubernetes-release/release/$(curl -s https://storage.googleapis.com/kubernetes-release/release/stable.txt)/bin/linux/amd64/kubectlTo 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 {{page.fullversion}} on Linux, type:
curl -LO https://storage.googleapis.com/kubernetes-release/release/{{page.fullversion}}/bin/linux/amd64/kubectl -
Make the kubectl binary executable.
chmod +x ./kubectl -
Move the binary in to your PATH.
sudo mv ./kubectl /usr/local/bin/kubectl
{% endcapture %}
{% capture win %}
-
Download the latest release {{page.fullversion}} from this link.
Or if you have
curlinstalled, use this command:curl -LO https://storage.googleapis.com/kubernetes-release/release/{{page.fullversion}}/bin/windows/amd64/kubectl.exeTo find out the latest stable version (for example, for scripting), take a look at https://storage.googleapis.com/kubernetes-release/release/stable.txt.
-
Add the binary in to your PATH.
{% endcapture %}
{% assign tab_names = "macOS,Linux,Windows" | split: ',' | compact %} {% assign tab_contents = site.emptyArray | push: macos | push: linux | push: win %}
{% include tabs.md %}
Download as part of the Google Cloud SDK
kubectl can be installed as part of the Google Cloud SDK.
-
Install the Google Cloud SDK.
-
Run the following command to install
kubectl:gcloud components install kubectl -
Run
kubectl versionto verify that the version you've installed is sufficiently up-to-date.
Install with snap on Ubuntu
kubectl is available as a snap application.
-
If you are on Ubuntu or one of other Linux distributions that support snap package manager, you can install with:
sudo snap install kubectl --classic -
Run
kubectl versionto verify that the version you've installed is sufficiently up-to-date.
Install with Homebrew on macOS
-
If you are on macOS and using Homebrew package manager, you can install with:
brew install kubectl -
Run
kubectl versionto verify that the version you've installed is sufficiently up-to-date.
Install with Powershell from PSGallery
-
If you are on Windows and using Powershell Gallery package manager, you can install and update with:
Install-Script -Name install-kubectl -Scope CurrentUser -Force install-kubectl.ps1 [-DownloadLocation <path>]
If no Downloadlocation is specified, kubectl will be installed in users temp Directory
2. The installer creates $HOME/.kube and instructs it to create a config file
3. Updating
re-run Install-Script to update the installer
re-run install-kubectl.ps1 to install latest binaries
Install with Chocolatey on Windows
-
If you are on Windows and using Chocolatey package manager, you can install with:
choco install kubernetes-cli -
Run
kubectl versionto verify that the version you've installed is sufficiently up-to-date. -
Configure kubectl to use a remote Kubernetes cluster:
cd C:\users\yourusername (Or wherever your %HOME% directory is) mkdir .kube cd .kube New-Item config -type file
Edit the config file with a text editor of your choice, such as Notepad for example.
Configure kubectl
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. 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.
By default, kubectl configuration is located at ~/.kube/config.
Check the kubectl configuration
Check that kubectl is properly configured by getting the cluster state:
kubectl cluster-info
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 correctly configured or not able to connect to a Kubernetes cluster.
The connection to the server <server-name:port> was refused - did you specify the right host or port?
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:
kubectl cluster-info dump
Enabling shell autocompletion
kubectl includes autocompletion support, which can save a lot of typing!
The completion script itself is generated by kubectl, so you typically just need to invoke it from your profile.
Common examples are provided here. For more details, consult kubectl completion -h.
On Linux, using bash
To add kubectl autocompletion to your current shell, run source <(kubectl completion bash).
To add kubectl autocompletion to your profile, so it is automatically loaded in future shells run:
echo "source <(kubectl completion bash)" >> ~/.bashrc
On macOS, using bash
On macOS, you will need to install bash-completion support via Homebrew first:
## If running Bash 3.2 included with macOS
brew install bash-completion
## or, if running Bash 4.1+
brew install bash-completion@2
Follow the "caveats" section of brew's output to add the appropriate bash completion path to your local .bashrc.
If you've installed kubectl using the Homebrew instructions then kubectl completion should start working immediately.
If you have installed kubectl manually, you need to add kubectl autocompletion to the bash-completion:
kubectl completion bash > $(brew --prefix)/etc/bash_completion.d/kubectl
The Homebrew project is independent from Kubernetes, so the bash-completion packages are not guaranteed to work.
Using Zsh
If you are using zsh edit the ~/.zshrc file and add the following code to enable kubectl autocompletion:
if [ $commands[kubectl] ]; then
source <(kubectl completion zsh)
fi
Or when using Oh-My-Zsh, edit the ~/.zshrc file and update the plugins= line to include the kubectl plugin.
source <(kubectl completion zsh)
{% endcapture %} {% capture whatsnext %} Learn how to launch and expose your application. {% endcapture %} {% include templates/task.md %}