Difference between revisions of "Kubernetes Cheat Sheet"

From Gejoreuy
Jump to navigation Jump to search
(Created page with "== Cheatsheet == https://kubernetes.io/docs/reference/kubectl/cheatsheet/ == Run Kubernetes Dashboard == Run this comand from kubernetes master. [root@gejoreuy-kubmas...")
 
 
(7 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Cheatsheet ==
+
'''Cheatsheet'''
  
 
https://kubernetes.io/docs/reference/kubectl/cheatsheet/
 
https://kubernetes.io/docs/reference/kubectl/cheatsheet/
  
  
== Run Kubernetes Dashboard ==
+
'''Run Kubernetes Dashboard'''
  
 
Run this comand from kubernetes master.
 
Run this comand from kubernetes master.
  
  [root@gejoreuy-kubmaster ~]# kubectl proxy --address 0.0.0.0
+
[root@gejoreuy-kubmaster ~]# kubectl proxy --address 0.0.0.0
  Starting to serve on [::]:8001
+
Starting to serve on [::]:8001
 
+
 
Then setup tunnels in Putty from localhost to port 8001.
 
Then setup tunnels in Putty from localhost to port 8001.
  
  
== Leave Kubernetes Master ==
+
'''Leave Kubernetes Master'''
  
 
Run below command in kubernetes node that want to leave the master.
 
Run below command in kubernetes node that want to leave the master.
  
  [root@gejoreuy-kubnode2 ~]# kubeadm reset
+
[root@gejoreuy-kubnode2 ~]# kubeadm reset
  
  
== Delete Node ==
+
'''Delete Node'''
  
 
After some node leave, this node which left has status NotReady in kubernetes master.
 
After some node leave, this node which left has status NotReady in kubernetes master.
 
    
 
    
  [root@gejoreuy-kubmaster ~]# kubectl get nodes
+
[root@gejoreuy-kubmaster ~]# kubectl get nodes
  gejoreuy-kubmaster  Ready      master  16h  v1.17.3
+
gejoreuy-kubmaster  Ready      master  16h  v1.17.3
  gejoreuy-kubnode1    Ready      <none>  16h  v1.17.3
+
gejoreuy-kubnode1    Ready      <none>  16h  v1.17.3
  gejoreuy-kubnode2    NotReady  <none>  16h  v1.17.3
+
gejoreuy-kubnode2    NotReady  <none>  16h  v1.17.3
 +
 
 +
 
 +
'''Scalling Deployments'''
 +
 
 +
To scaling up or scalling down deployment services in Kubernetes.
 +
 
 +
[root@gejoreuy-kubmaster ~]# kubectl -n [namespace] scale --replicas=[replica-count] deployment/[service-name] --insecure-skip-tls-verify=true
 +
 
 +
 
 +
'''Check CPU and Memory LImits and Request for Pods'''
 +
 
 +
Change <node-name> with correct node name.
 +
 
 +
[root@gejoreuy-kubmaster ~]# kubectl get po -o custom-columns="Node:spec.nodeName,Namespace:metadata.namespace,Name:metadata.name,CPU-limit:spec.containers[*].resources.limits.cpu, CPU-request:spec.containers[*].resources.requests.cpu, memory-limits:spec.containers[*].resources.limits.memory, memory-request:spec.containers[*].resources.requests.memory" -A --sort-by="spec.containers[*].resources.limits.memory" --field-selector=spec.nodeName=<node-name>
 +
 
 +
'''Get Secret'''
 +
 
 +
Get secret and decode it from base64 version.
 +
 
 +
[root@gejoreuy-kubmaster ~]# kubectl -n [namespace] get secret [secretname] -o jsonpath='{.data}'
 +
[root@gejoreuy-kubmaster ~]# echo 'SECRETRESULSECRETRESULTSECRETRESULT' | base64 -d

Latest revision as of 16:12, 29 May 2024

Cheatsheet

https://kubernetes.io/docs/reference/kubectl/cheatsheet/


Run Kubernetes Dashboard

Run this comand from kubernetes master.

[root@gejoreuy-kubmaster ~]# kubectl proxy --address 0.0.0.0
Starting to serve on [::]:8001

Then setup tunnels in Putty from localhost to port 8001.


Leave Kubernetes Master

Run below command in kubernetes node that want to leave the master.

[root@gejoreuy-kubnode2 ~]# kubeadm reset


Delete Node

After some node leave, this node which left has status NotReady in kubernetes master.

[root@gejoreuy-kubmaster ~]# kubectl get nodes
gejoreuy-kubmaster   Ready      master   16h   v1.17.3
gejoreuy-kubnode1    Ready      <none>   16h   v1.17.3
gejoreuy-kubnode2    NotReady   <none>   16h   v1.17.3


Scalling Deployments

To scaling up or scalling down deployment services in Kubernetes.

[root@gejoreuy-kubmaster ~]# kubectl -n [namespace] scale --replicas=[replica-count] deployment/[service-name] --insecure-skip-tls-verify=true


Check CPU and Memory LImits and Request for Pods

Change <node-name> with correct node name.

[root@gejoreuy-kubmaster ~]# kubectl get po -o custom-columns="Node:spec.nodeName,Namespace:metadata.namespace,Name:metadata.name,CPU-limit:spec.containers[*].resources.limits.cpu, CPU-request:spec.containers[*].resources.requests.cpu, memory-limits:spec.containers[*].resources.limits.memory, memory-request:spec.containers[*].resources.requests.memory" -A --sort-by="spec.containers[*].resources.limits.memory" --field-selector=spec.nodeName=<node-name>

Get Secret

Get secret and decode it from base64 version.

[root@gejoreuy-kubmaster ~]# kubectl -n [namespace] get secret [secretname] -o jsonpath='{.data}'
[root@gejoreuy-kubmaster ~]# echo 'SECRETRESULSECRETRESULTSECRETRESULT' | base64 -d