https://github.com/eon01/KubectlCheatSheet

The Definitive Kubectl Sheetcheat. ⭐ Give it a star if you like it. Work (always) in progress !
https://github.com/eon01/KubectlCheatSheet

cheatsheet cheatsheets kubectl kubernetes snippets

Last synced: 6 days ago
JSON representation

The Definitive Kubectl Sheetcheat. ⭐ Give it a star if you like it. Work (always) in progress !

• Host: GitHub
• URL: https://github.com/eon01/KubectlCheatSheet
• Owner: eon01
• Created: 2020-11-25T20:27:13.000Z (almost 4 years ago)
• Default Branch: main
• Last Pushed: 2023-12-24T08:49:28.000Z (11 months ago)
• Last Synced: 2024-09-05T13:13:38.794Z (about 2 months ago)
• Topics: cheatsheet, cheatsheets, kubectl, kubernetes, snippets
• Homepage:
• Size: 702 KB
• Stars: 187
• Watchers: 8
• Forks: 77
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        

# 👌 Kubectl Cheatsheet

🍴 Fork and contribute. Your contribution is welcome 🙌

# Sponsors

## 📚 Cloud Native Microservices With Kubernetes

A Comprehensive Guide to Building, Scaling, Deploying, Observing, and Managing Highly-Available Microservices in Kubernetes. A comprehensive and example-rich guide suitable for learners of all levels. Get the book [on Amazon](https://www.amazon.com/Cloud-Native-Microservices-Kubernetes-Highly-Available-ebook/dp/B0C923BYSL?&linkCode=ll1&tag=eon01-20&linkId=a78552e5f2c08434be802425be87a91a&language=en_US&ref_=as_li_ss_tl).

## ❤️ Kaptain, Kubernetes Weekly Newsletter

Curated Kubernetes news, tutorials, tools, research papers, jobs, and more - delivered to your inbox every week. [Subscribe and start receiving our free weekly newsletter](https://faun.dev/newsletter/kaptain).

## 🛍️ Show off your love for all things TECH

If you're seeking a cozy sweatshirt to wear during your extended coding sessions or a mug to exhibit your passion for programming, [you can find it all on ByteVibe](https://bytevibe.co/)

# TOC

- [Pods](#pods)

  * [List all pods in namespace ``](#list-all-pods-in-namespace---default--)

  * [View a pod in watch mode](#view-a-pod-in-watch-mode)

  * [View all pods in watch mode](#view-all-pods-in-watch-mode)

  * [List sorted pods](#list-sroted-pods)

  * [List pods using a different output](#list-pods-using-a-different-output)

  * [Formatting output](#formatting-output)

  * [List all pods in a namespace](#list-all-pods-in-a-namespace)

  * [List all pods in all namespaces](#list-all-pods-in-all-namespaces)

  * [Create from an image](#create-from-an-image)

  * [Run pod in an interactive shell mode](#run-pod-in-an-interactive-shell-mode)

  * [Run a command after creating a pod](#run-a-command-after-creating-a-pod)

  * [Executing a command in a running pod](#executing-a-command-in-a-running-pod)

  * [Create a pod: dry run mode (without really creating it)](#create-a-pod--dry-run-mode--without-really-creating-it-)

  * [Patch a pod](#patch-a-pod)

  * [Create from a YAML file](#create-from-a-yaml-file)

  * [Export YAML from the dry run mode](#export-yaml-from-the-dry-run-mode)

  * [Create from STDIN](#create-from-stdin)

  * [Create multiple resources from STDIN](#create-multiple-resources-from-stdin)

  * [Create in a namespace](#create-in-a-namespace)

  * [Create in a namespace from a file](#create-in-a-namespace-from-a-file)

  * [Delete pods](#delete-pods)

  * [Get pod logs](#get-pod-logs)

  * [List all container id of init container of all pods](#list-all-container-id-of-init-container-of-all-pods)

  * [Show metrics for a given pod](#show-metrics-for-a-given-pod)

  * [Show metrics for a given pod and all its containers](#show-metrics-for-a-given-pod-and-all-its-containers)

- [Deployments](#deployments)

  * [Create a deployment](#create-a-deployment)

  * [Create a deployment with a predefined replica number](#create-a-deployment-with-a-predefined-replica-number)

  * [Create a deployment with a predefined replica number and opening a port](#create-a-deployment-with-a-predefined-replica-number-and-opening-a-port)

  * [Create a deployment with a predefined replica number, opening a port and exposing it](#create-a-deployment-with-a-predefined-replica-number--opening-a-port-and-exposing-it)

  * [Get a deployment](#get-a-deployment)

  * [Watch a deployment](#watch-a-deployment)

  * [List all deployments](#list-all-deployments)

  * [Update the image](#update-the-image)

  * [Scale a deployment](#scale-a-deployment)

  * [Dry run and YAML output](#dry-run-and-yaml-output)

  * [Create a deployment from a file](#create-a-deployment-from-a-file)

  * [Edit a deployment](#edit-a-deployment)

  * [Rollback deployment](#rollback-deployment)

  * [Get rollout history](#get-rollout-history)

  * [Roll back to a previous revision](#roll-back-to-a-previous-revision)

  * [Execute deployment rollout operations](#execute-deployment-rollout-operations)

- [Port Forwarding](#port-forwarding)

  * [Choosing localhost port](#choosing-localhost-port)

  * [Listening on the same port](#listening-on-the-same-port)

  * [Listen on a random port locally](#listen-on-a-random-port-locally)

  * [Listen on port on localhost + another IP](#listen-on-port-on-localhost---another-ip)

  * [Listen on a forwarded port on all addresses](#listen-on-a-forwarded-port-on-all-addresses)

- [Services](#services)

  * [Create a service](#create-a-service)

  * [Delete service(s)](#delete-service-s-)

  * [Describe a service](#describe-a-service)

- [Nodes](#nodes)

  * [Get node](#get-node)

  * [Get a specific node](#get-a-specific-node)

  * [Show node metrics](#show-node-metrics)

  * [Get external IPs of cluster nodes](#get-external-ips-of-cluster-nodes)

  * [Describe commands with verbose output](#describe-commands-with-verbose-output)

  * [Check which nodes are ready](#check-which-nodes-are-ready)

  * [Mark a node as unschedulable](#mark-a-node-as-unschedulable)

  * [Drain a node for maintenance](#drain-a-node-for-maintenance)

  * [Mark a node as schedulable](#mark-a-node-as-schedulable)

- [Namespaces](#namespaces)

  * [List namespaces](#list-namespaces)

  * [List or describe a namespace](#list-or-describe-a-namespace)

  * [Create namespace](#create-namespace)

  * [Delete namespace](#delete-namespace)

- [Service accounts](#service-accounts)

  * [List service accounts](#list-service-accounts)

  * [Get a service account](#get-a-service-account)

  * [Create a service account](#create-a-service-account)

  * [Delete a service account](#delete-a-service-account)

  * [Describe a service account](#describe-a-service-account)

- [Events](#events)

  * [List events](#list-events)

  * [List sorted events](#list-sorted-events)

  * [List formatted events](#list-formatted-events)

- [Documentation](#documentation)

  * [Get the documentation for pod manifests](#get-the-documentation-for-pod-manifests)

  * [Get the documentation for service manifests](#get-the-documentation-for-service-manifests)

- [Describing resources](#describing-resources)

- [Editing resources](#editing-resources)

  * [Edit a service](#edit-a-service)

  * [Edit a service with your favorite text editor](#edit-a-service-with-your-favorite-text-editor)

- [Deleting Resources](#deleting-resources)

  * [Delete a resource using the type and name specified in ``](#delete-a-resource-using-the-type-and-name-specified-in---file--)

  * [Delete pods and services with same names](#delete-pods-and-services-with-same-names)

  * [Delete pods and services with a custom label](#delete-pods-and-services-with-a-custom-label)

  * [Delete all pods and services in a namespace](#delete-all-pods-and-services-in-a-namespace)

  * [Delete all resources in a namespace](#delete-all-resources-in-a-namespace)

- [All get commands](#all-get-commands)

- [Abbreviations / Short forms of resource types](#abbreviations---short-forms-of-resource-types)

- [Verbose Kubectl](#verbose-kubectl)

- [Cluster](#cluster)

  * [Display addresses of the master and services](#display-addresses-of-the-master-and-services)

  * [Dump cluster state to STDOUT](#dump-cluster-state-to-stdout)

  * [Dump cluster state to a file](#dump-cluster-state-to-a-file)

  * [Compares the current cluster state against the state that the cluster would be in if the manifest was applied](#compares-the-current-cluster-state-against-the-state-that-the-cluster-would-be-in-if-the-manifest-was-applied)

  * [List all images running in a cluster](#list-all-images-running-in-a-cluster)

- [Kubectl context](#kubectl-context)

  * [Show merged kubeconfig settings](#show-merged-kubeconfig-settings)

  * [Use multiple kubeconfig](#use-multiple-kubeconfig)

    + [Get a list of users](#get-a-list-of-users)

  * [Display the first user](#display-the-first-user)

  * [Get the password for the "admin" user](#get-the-password-for-the--admin--user)

    + [Display the current context](#display-the-current-context)

    + [Display list of contexts](#display-list-of-contexts)

    + [Set the default context to ``](#set-the-default-context-to---cluster--)

  * [Sets a user entry in kubeconfig](#sets-a-user-entry-in-kubeconfig)

  * [Sets a user with a client key](#sets-a-user-with-a-client-key)

  * [Sets a user with basic auth](#sets-a-user-with-basic-auth)

  * [Sets a user with client certificate](#sets-a-user-with-client-certificate)

  * [Set a context utilizing a specific config file](#set-a-context-utilizing-a-specific-config-file)

  * [Set a context utilizing a specific username and namespace.](#set-a-context-utilizing-a-specific-username-and-namespace)

- [Alias](#alias)

  * [Create an alias on *nix](#create-an-alias-on--nix)

  * [Create an alias on Windows](#create-an-alias-on-windows)

- [Kubectl imperative (create) vs declarative (apply)](#kubectl-imperative--create--vs-declarative--apply-)

  * [Create](#create)

  * [Apply](#apply)

## Pods

### List all pods in namespace ``

```

kubectl get pods

```

or 

```

kubectl get pod

```

or

```

kubectl get po

```

### View a pod in watch mode

```

kubectl get pod  --watch

```

### View all pods in watch mode

```

kubectl get pods -A --watch

```

### List sroted pods 

```

kubectl get pods --sort-by='.status.containerStatuses[0].restartCount'

```

### List pods using a different output

```

kubectl get pods -o 

```

Examples: 

- JSON output

```

kubectl get pods -o json

```

or

```

kubectl get pods -ojson

```

or

```

kubectl get pods -o=json

```

- Wide output:

```

kubectl get pods -o wide

```

- Custom columns:

```

kubectl get pods -o custom-columns='DATA:spec.containers[*].image'

```

or 

```

kubectl get pods -o custom-columns='DATA:spec.containers[*].volumeMounts'

```

or

```

kubectl get pods -o custom-columns='DATA:metadata.*'

```

### Formatting output

To output details to your terminal window in a specific format, add the `-o` (or `--output`) flag to a supported `kubectl` command (source: [K8s docs](https://kubernetes.io/docs))

Output format | Description

--------------| -----------

`-o=custom-columns=` | Print a table using a comma separated list of custom columns

`-o=custom-columns-file=` | Print a table using the custom columns template in the `` file

`-o=json`     | Output a JSON formatted API object

`-o=jsonpath=` | Print the fields defined in a [jsonpath](/docs/reference/kubectl/jsonpath) expression

`-o=jsonpath-file=` | Print the fields defined by the [jsonpath](/docs/reference/kubectl/jsonpath) expression in the `` file

`-o=name`     | Print only the resource name and nothing else

`-o=wide`     | Output in the plain-text format with any additional information, and for pods, the node name is included

`-o=yaml`     | Output a YAML formatted API object

### List all pods in a namespace

```

kubectl get pods -n 

```

or 

```

kubectl -n  get pods 

```

or 

```

kubectl --namespace  get pods 

```

### List all pods in all namespaces

```

kubectl get pods --all-namespaces

```

or

```

kubectl get pods -A

```

### Create from an image

```

kubectl run  --generator=run-pod/v1 --image=

```

In the following cheatsheet, we will be using images such as nginx or busybox.

Example:

```

kubectl run nginx --generator=run-pod/v1 --image=nginx

```

```

kubectl run busybox --generator=run-pod/v1 --image=busybox

```

### Run pod in an interactive shell mode

```

kubectl run -i --tty nginx --image=nginx -- sh 

```

### Run a command after creating a pod

```

kubectl run busybox --image=busybox -- sleep 100000

```

### Executing a command in a running pod

```

kubectl exec  -- 

```

Or pass stdin to the container in TTY mode:

```

kubectl exec -it  -- 

```

Example:

```

kubectl exec -it nginx -- ls -lrth /app/

```

### Create a pod: dry run mode (without really creating it)

```

kubectl run  --generator=run-pod/v1 --image=nginx --dry-run 

```

### Patch a pod

```

kubectl patch pod  -p ''

```

Example:

```

kubectl patch pod  -p  '{"spec":{"containers":[{"name":"kubernetes-serve-hostname","image":"new image"}]}}'

```

Another example:

```

kubectl patch pod valid-pod --type='json' -p='[{"op": "replace", "path": "/spec/containers/0/image", "value":"new image"}]'

```

### Create from a YAML file

```

kubectl create -f pod.yaml

```

### Export YAML from the dry run mode

```

kubectl run nginx --generator=run-pod/v1 --image=nginx --dry-run -o yaml

```

### Create from STDIN

```

cat <

```

### Create in a namespace from a file

```

kubectl create -f pod.yaml -n 

```

### Delete pods

```

kubectl delete pod/

```

or 

```

kubectl delete pod  

```

If you create the pod from a file, you can also use:

```

kubectl delete -f pod.yaml 

```

To force deletion:

```

kubectl delete pod  --grace-period=0 --force

```

### Get pod logs

```

kubectl logs 

```

or

Sometimes a pod contains more than 1 container. You need to filter the output to get logs for a specific container(s)

```

kubectl logs  -c 

```

To follow the logs output (tail -f):

```

kubectl logs -f 

```

If you need to output the logs for all pods with a label

```

kubectl logs -l =

```

Example:

```

kubectl logs -l env=prod

```

You can also view logs in a multi container case with labels:

```

kubectl logs -l = -c 

```

Or view all cotainers logs with a given label:

```

kubectl logs -f -l = --all-containers

```

### List all container id of init container of all pods

```

kubectl get pods --all-namespaces -o jsonpath='{range .items[*].status.initContainerStatuses[*]}{.containerID}{"\n"}{end}' | cut -d/ -f3

```

### Show metrics for a given pod

```

kubectl top pod 

```

### Show metrics for a given pod and all its containers

```

kubectl top pod  --containers               

```

## Deployments

### Create a deployment

```

kubectl run  --image=

```

or

```

kubectl create deployment  --image=

```

### Create a deployment with a predefined replica number

```

kubectl run  --image= --replicas=

```

### Create a deployment with a predefined replica number and opening a port

```

kubectl run  --image= --replicas= --port=

```

Example:

```

kubectl run nginx --image=nginx --replicas=2 --port=80

```

**Note**: The default generator for `kubectl run` is `--generator=deployment/apps.v1`.

**Note**: `--generator=deployment/apps.v1` is deprecated and will be removed in future versions. Use kubectl run `--generator=run-pod/v1` or `kubectl create` instead.

### Create a deployment with a predefined replica number, opening a port and exposing it

```

kubectl run nginx --image=nginx --replicas=2 --port=80 --expose

```

### Get a deployment

```

kubectl get deploy 

```

### Watch a deployment

```

kubectl get deployment  --watch

```

or 

```

kubectl get deployment  -w

```

Or using a shorter version:

```

kubectl get deploy  -w

```

Or even the longer one:

```

kubectl get deployments.apps  --watch

```

### List all deployments

Same as listing pods, you have multiple options from namespace to output formatters:

```

kubectl get deploy -n 

kubectl get deploy --all-namespaces 

kubectl get deploy -A

kubectl get deploy -oyaml

kubectl get deploy -owide

```

### Update the image

Rolling update "nginx" containers of "nginx" deployment, updating the image:

```

kubectl set image deployment/nginx nginx=nginx:1.9.1

```

Rolling update "api" containers of "backend" deployment, updating the image:

```

kubectl set image deployment/backend api=image:v2

```

### Scale a deployment

```

kubectl scale --replicas=5 deployment/

```

**Note**: You can use a shorter version: 

```

kubectl scale --replicas=5 deploy/

```

### Dry run and YAML output

```

kubectl run nginx --image=nginx --replicas=2 --port=80 --dry-run -o yaml

```

### Create a deployment from a file

```

kubectl apply -f deployment.yaml

```

### Edit a deployment

```

kubectl edit deployment/

```

### Rollback deployment 

After editing your deployment, you had an error, a solution can be rolling back to the old deployment status:

```

kubectl rollout undo deployment 

```

### Get rollout history

You can check the rollout history:

```

kubectl rollout history deployment 

```

```

kubectl rollout history deployment 

```

Example:

```

kubectl rollout history deployment nginx

```

gives you:

```

REVISION  CHANGE-CAUSE

2         kubectl set image deployment/nginx nginx=nginx:1.9.1 --record=true

3         

```

### Roll back to a previous revision

Using the information from the rollout history, we can get back our deployment to a given revision:

```

kubectl rollout undo deployment  --to-revision=

```

Example:

```

kubectl rollout undo deployment nginx --to-revision=2

```

### Execute deployment rollout operations

```

kubectl rollout status deployment 

kubectl rollout pause deployment 

kubectl rollout resume deployment 

```

## Port Forwarding

### Choosing localhost port

```

kubectl port-forward deployment   :

kubectl port-forward pod   :

```

Example:

Forward to localhost 8090 from pod 6379:

```

kubectl port-forward redis 8090:6379

```

### Listening on the same port

```

kubectl port-forward pod  

```

Example: Listen on ports 8000 and 9000 on localhost, forwarded from the same ports in the pod (8000 and 9000)

```

kubectl port-forward pod nginx 8000 9000

```

### Listen on a random port locally

```

kubectl port-forward pod  :

```

Example:

```

kubectl port-forward pod nginx :80

```

### Listen on port on localhost + another IP

```

kubectl port-forward --address localhost, pod  :

```

Example:

```

kubectl port-forward --address localhost,10.10.10.1 pod redis 8090:6379

```

### Listen on a forwarded port on all addresses 

```

kubectl port-forward --address 0.0.0.0 pod  :

```

## Services

### Create a service

```

kubectl create service   [flags] [options]>

```

Examples:

```

kubectl create service clusterip myclusterip --tcp=5678:8080

kubectl create service  loadbalancer myloadbalancer --tcp=80

```

You can use `svc` instead of `service`.

### Delete service(s)

```

kubectl delete service myclusterip

kubectl delete service myloadbalancer

kubectl delete svc myclusterip

kubectl delete svc myloadbalancer

```

or 

```

kubectl delete service myclusterip myloadbalancer

```

### Describe a service

```

kubectl describe service 

```

## Nodes

### Get node

```

kubectl get nodes

```

### Get a specific node

```

kubectl get nodes 

```

### Show node metrics

```

kubectl top node 

```

### Get external IPs of cluster nodes

```

kubectl get nodes -o jsonpath='{.items[*].status.addresses[?(@.type=="ExternalIP")].address}'

```

### Describe commands with verbose output

```

kubectl describe nodes 

```

### Check which nodes are ready

```

JSONPATH='{range .items[*]}{@.metadata.name}:{range @.status.conditions[*]}{@.type}={@.status};{end}{end}' && kubectl get nodes -o jsonpath="$JSONPATH" | grep "Ready=True"

```

### Mark a node as unschedulable

```

kubectl cordon 

```

### Drain a node for maintenance

```

kubectl drain 

```

### Mark a node as schedulable

```

kubectl uncordon 

```

## Namespaces

### List namespaces

```

kubectl get namespaces 

```

or

```

kubectl get ns 

```

### List or describe a namespace

```

kubectl get namespace 

kubectl describe namespace 

```

### Create namespace

```

kubectl create namespace 

```

or 

```

kubectl create -f namespace.yaml

```

or 

```

cat < 

```

or 

```

kubectl delete -f namespace.yaml

```

## Service accounts

### List service accounts

```

kubectl get serviceaccounts

```

or 

```

kubectl get sa

```

### Get a service account

```

kubectl get serviceaccount 

```

or

```

kubectl get serviceaccounts 

```

or

```

kubectl get sa 

```

or 

```

kubectl get sa/

```

### Create a service account

```

kubectl create serviceaccount 

```

### Delete a service account

```

kubectl delete serviceaccount  

```

or 

```

kubectl delete -f myserviceaccount.yaml

```

### Describe a service account	

```

kubectl describe serviceaccount  

```

## Events

### List events

```

kubectl get events -A

```

### List sorted events

```

kubectl get events --sort-by=

```

Example: Sorted by timestamp

```

kubectl get events --sort-by=.metadata.creationTimestamp

```

### List formatted events

```

kubectl get events -o 

```

Example:

```

kubectl get events -owide

```

## Documentation

### Get the documentation for pod manifests

```

kubectl explain pod

```

### Get the documentation for service manifests

```

kubectl explain service

```

## Describing resources

```

kubectl describe  

```

Example:

```

kubectl describe pod busybox

```

or 

```

kubectl describe nodes minikube 

```

Other possible resources you can use with `describe`:

```

apiservices.apiregistration.k8s.io

certificatesigningrequests.certificates.k8s.io

clusterrolebindings.rbac.authorization.k8s.io

clusterroles.rbac.authorization.k8s.io

componentstatuses

configmaps

controllerrevisions.apps

cronjobs.batch

csidrivers.storage.k8s.io

csinodes.storage.k8s.io

customresourcedefinitions.apiextensions.k8s.io

daemonsets.apps

daemonsets.extensions

deployments.apps

deployments.extensions

endpoints

events

events.events.k8s.io

horizontalpodautoscalers.autoscaling

ingresses.extensions

ingresses.networking.k8s.io

jobs.batch

leases.coordination.k8s.io

limitranges

mutatingwebhookconfigurations.admissionregistration.k8s.io

namespaces

networkpolicies.extensions

networkpolicies.networking.k8s.io

nodes

persistentvolumeclaims

persistentvolumes

poddisruptionbudgets.policy

pods

podsecuritypolicies.extensions

podsecuritypolicies.policy

podtemplates

priorityclasses.scheduling.k8s.io

replicasets.apps

replicasets.extensions

replicationcontrollers

resourcequotas

rolebindings.rbac.authorization.k8s.io

roles.rbac.authorization.k8s.io

runtimeclasses.node.k8s.io

secrets

serviceaccounts

services

statefulsets.apps

storageclasses.storage.k8s.io

validatingwebhookconfigurations.admissionregistration.k8s.io

volumeattachments.storage.k8s.io

```

## Editing resources

### Edit a service

```

kubectl edit service                     

```

### Edit a service with your favorite text editor

```

KUBE_EDITOR="vim" edit service   

```

**Note**: Change `service` by any editable resource type like pods.

## Deleting Resources

### Delete a resource using the type and name specified in ``

```

kubectl delete -f       

```

### Delete pods and services with same names 

```

kubectl delete pod,service  

```

### Delete pods and services with a custom label

```

kubectl delete pods,services -l =

```

### Delete all pods and services in a namespace

```  

kubectl -n  delete pods,services --all              

```

### Delete all resources in a namespace

```

kubectl delte 

```

## All get commands 

```

kubectl get all

kubectl get pods

kubectl get replicasets

kubectl get services

kubectl get nodes

kubectl get namespaces

kubectl get configmaps

kubectl get endpoints 

```

## Abbreviations / Short forms of resource types

|      Resource type       |   Abbreviations   |

|--------------------------|-------------------|

| componentstatuses        | cs                |

| configmaps               | cm                |

| daemonsets               | ds                |

| deployments              | deploy            |

| endpoints                | ep                |

| event                    | ev                |

| horizontalpodautoscalers | hpa               |

| ingresses                | ing               |

| limitranges              | limits            |

| namespaces               | ns                |

| nodes                    | no                |

| persistentvolumeclaims   | pvc               |

| persistentvolumes        | pv                |

| pods                     | po                |

| podsecuritypolicies      | psp               |

| replicasets              | rs                |

| replicationcontrollers   | rc                |

| resourcequotas           | quota             |

| serviceaccount           | sa                |

| services                 | svc               |

## Verbose Kubectl

```

kubectl run nginx  --image=nginx --v=5

```

Verbosity | Description

--------------| -----------

`--v=0` | Generally useful for this to *always* be visible to a cluster operator.

`--v=1` | A reasonable default log level if you don't want verbosity.

`--v=2` | Useful steady state information about the service and important log messages that may correlate to significant changes in the system. This is the recommended default log level for most systems.

`--v=3` | Extended information about changes.

`--v=4` | Debug level verbosity.

`--v=6` | Display requested resources.

`--v=7` | Display HTTP request headers.

`--v=8` | Display HTTP request contents.

`--v=9` | Display HTTP request contents without truncation of contents.

(Table source: [K8s docs](https://kubernetes.io/docs))

## Cluster

### Display addresses of the master and services

```

kubectl cluster-info                        

```

### Dump cluster state to STDOUT

```

kubectl cluster-info dump           

```

### Dump cluster state to a file

```

kubectl cluster-info dump --output-directory=

```

### Compares the current cluster state against the state that the cluster would be in if the manifest was applied

```

kubectl diff -f ./my-manifest.yaml

```

### List all images running in a cluster

```

kubectl get pods -A -o=custom-columns='DATA:spec.containers[*].image'

```

## Kubectl context

### Show merged kubeconfig settings

```

kubectl config view 

```

### Use multiple kubeconfig 

```

KUBECONFIG=~/.kube/config1:~/.kube/config2:~/.kube/config3

```

#### Get a list of users

```

kubectl config view -o jsonpath='{.users[*].name}'

```

### Display the first user

```

kubectl config view -o jsonpath='{.users[].name}'

```

### Get the password for the "admin" user

```

kubectl config view -o jsonpath='{.users[?(@.name == "admin")].user.password}'

```

#### Display the current context

```

kubectl config current-context

```

#### Display list of contexts 

```

kubectl config get-contexts

```

#### Set the default context to ``

```

kubectl config use-context 

```

### Sets a user entry in kubeconfig

```

kubectl config set-credentials  [options]

```

### Sets a user with a client key

```

kubectl config set-credentials  --client-key=~/.kube/admin.key

```

### Sets a user with basic auth

```

kubectl config set-credentials --username= --password=

```

### Sets a user with client certificate

```

kubectl config set-credentials  --client-certificate= --embed-certs=true

```

### Set a context utilizing a specific config file

```

kubectl config --kubeconfig= use-context 

```

### Set a context utilizing a specific username and namespace.

```

kubectl config set-context gce --user=cluster-admin --namespace=foo \

  && kubectl config use-context gce

```

##  Alias

### Create an alias on *nix

```

alias k=kubectl

```

### Create an alias on Windows

```

Set-Alias -Name k -Value kubectl

```

## Kubectl imperative (create) vs declarative (apply)

### Create

You tell your cluster what you want to create, replace or delete, not how you want you it to look like.

```

kubectl create -f 

kubectl delete deployment 

kubectl delete deployment 

kubectl delete deployment 

```

### Apply

You tell your cluster how you want it to look like.

The creation, deletion and modification of objects is done via a single command. The declarative approach is a statement of the desired end result. 

```

kubectl apply -f 

kubectl delete -f 

kubectl apply -f 

```

If the deployment is deleted in ``, it will also be deleted from the cluster.