Kubectl: Difference between revisions

From Chorke Wiki
Jump to navigation Jump to search
Line 30: Line 30:
* '''A user''' is a credential used to interact with the Kubernetes API.
* '''A user''' is a credential used to interact with the Kubernetes API.
* '''A context''' is a combination of a cluster and a user. Every time you execute an <code>oc</code> or <code>kubectl</code> command, you reference a context inside <code>kubeconfig</code>.
* '''A context''' is a combination of a cluster and a user. Every time you execute an <code>oc</code> or <code>kubectl</code> command, you reference a context inside <code>kubeconfig</code>.


<source lang="bash">
<source lang="bash">
export KUBECONFIG="$HOME/.kube/chorke-academia-kubeconfig.yaml"
export KUBECONFIG=$HOME/.kube/chorke-academia-kubeconfig.yaml
chmod 600 $HOME/.kube/chorke-academia-kubeconfig.yaml
</source>
</source>
==Knowledge==
{|
|valign='top'|
kubectl get deployment -A
kubectl get services -A
kubectl get events -A
kubectl get pods -A
helm list
|valign='top'|
|valign='top'|
|-
|colspan='3'|
----
|-
|valign='top'|
sudo ss -tulwn | grep LISTEN
sudo ss -tulpn | grep LISTEN
sudo ss -tulpn | grep LISTEN | grep sshd
sudo ss -tulpn | grep LISTEN | grep minio
sudo ss -tulpn | grep LISTEN | grep resolve
|valign='top'|
sudo lsof -i -P -n | grep LISTEN
|valign='top'|
|}


==References==
==References==

Revision as of 01:40, 13 April 2023

sudo curl -fsSLo /etc/apt/keyrings/kubernetes-archive-keyring.gpg\
 https://packages.cloud.google.com/apt/doc/apt-key.gpg

cat << EOF | sudo tee /etc/apt/sources.list.d/kubernetes.list >/dev/null
deb [arch=$(dpkg --print-architecture)\
 signed-by=/etc/apt/keyrings/kubernetes-archive-keyring.gpg]\
 https://apt.kubernetes.io/ kubernetes-xenial main
EOF
sudo apt update && sudo apt install -y apt-transport-https curl
sudo apt install -y docker-ce=5:20.10.14~3-0~ubuntu-focal\
 kubelet=1.23.5-00 kubeadm=1.23.5-00 kubectl=1.23.5-00

sudo apt-mark hold docker-ce kubelet kubeadm kubectl
sudo apt install docker-compose

Kubeconfig

Kubernetes components like kubelet, kube-controller-manager, or kubectl use the kubeconfig file to interact with the Kubernetes API. Usually, the kubectl or oc commands use the kubeconfig file.

The kubeconfig file's default location for kubectl or oc is the ~/.kube directory. Instead of using the full kubeconfig name, the file is just named config. The default location of the kubeconfig file is ~/.kube/config. There are other ways to specify the kubeconfig location, such as the KUBECONFIG environment variable or the kubectl --kubeconfig parameter.


The kubeconfig file is a YAML file containing groups of clusters, users, and contexts.

  • A cluster is a Kubernetes or OpenShift cluster.
  • A user is a credential used to interact with the Kubernetes API.
  • A context is a combination of a cluster and a user. Every time you execute an oc or kubectl command, you reference a context inside kubeconfig.


export KUBECONFIG=$HOME/.kube/chorke-academia-kubeconfig.yaml
chmod 600 $HOME/.kube/chorke-academia-kubeconfig.yaml

Knowledge

kubectl get deployment -A
kubectl get services -A
kubectl get events -A
kubectl get pods -A
helm list

sudo ss -tulwn | grep LISTEN
sudo ss -tulpn | grep LISTEN
sudo ss -tulpn | grep LISTEN | grep sshd
sudo ss -tulpn | grep LISTEN | grep minio
sudo ss -tulpn | grep LISTEN | grep resolve
sudo lsof -i -P -n | grep LISTEN

References