{"id":14956,"date":"2022-02-04T10:33:12","date_gmt":"2022-02-04T10:33:12","guid":{"rendered":"https:\/\/linuxways.net\/?p=14956"},"modified":"2022-02-04T10:33:12","modified_gmt":"2022-02-04T10:33:12","slug":"kubectl-get-command-explained-with-examples","status":"publish","type":"post","link":"https:\/\/linuxways.net\/de\/centos\/kubectl-get-command-explained-with-examples\/","title":{"rendered":"‘kubectl get’ Command Explained with Examples"},"content":{"rendered":"

Kubernetes is an open-source platform that is the most portable for managing containerized workloads and services. It works as an automation tool by providing the services, support and tools that are widely available.<\/p>\n

Whereas, Kubectl controls the Kubernetes Cluster as it is one of the key components of Kubernetes having the capability to manage the nodes in the cluster. Kubectl get command is capable of fetching the related data on the cluster about the Kubernetes resources.<\/p>\n

In this article, we are going to discuss the use of the \u2018Kubectl get\u2019 command with some examples.<\/p>\n

Kubectl get commands<\/h2>\n

Some of the important kubectl get commands to fetch the data on the cluster about the Kubernetes resources are listed below.<\/p>\n

Kubectl get pod<\/h3>\n

To get the details about the pod of the container of the related kubernetes cluster, there is a command similar to the command as:<\/p>\n

To get the list of all the pods available on default namespace, run the command as shown below.<\/p>\n

$ kubectl get pod<\/pre>\n
But to get the details of the specific pod, you can enter the pod name as:<\/p>\n
$ kubectl get pod <pod name><\/pre>\n
Example<\/strong>:<\/p>\n
$ kubectl get pod nginx-http-6cf5c9bf86-p5q2x<\/pre>\n
<\/p>\n
Here, the pod name is \u201cnginx-http-6cf5c9bf86-p5q2x\u201d. It will display all the details regarding the specific pod.<\/p>\n
Kubectl get deployment<\/h3>\n
To get the details about the deployments of the container of the related kubernetes cluster, there is a command similar to the command as:<\/p>\n
To get the list of all the deployments available on default namespace, run the command as shown below.<\/p>\n
$ kubectl get deployment<\/pre>\n
But to get the details of the specific deployment, you can enter the deployment name as:<\/p>\n
$ kubectl get deployment <deployment name><\/pre>\n
Example<\/strong>:<\/p>\n
$ kubectl get deployment nginx-http<\/pre>\n
<\/p>\n
Here, the deployment name is \u201cnginx-http\u201d. It will display all the details regarding the specific deployment.<\/p>\n
Kubectl get service<\/h3>\n
To get the details about the service of the container of the related kubernetes cluster, there is a command similar to the command as:<\/p>\n
To get the list of all the services available on default namespace, run the command as shown below.<\/p>\n
$ kubectl get service<\/pre>\n
But to get the details of the specific service, you can enter the service name as:<\/p>\n
$ kubectl get service <service name><\/pre>\n
Example<\/strong>:<\/p>\n
$ kubectl get service nginx-http-svc<\/pre>\n
<\/p>\n
Here, the service name is \u201cnginx-http-svc\u201d. It will display all the details regarding the specific service.<\/p>\n
Kubectl get ingress<\/h3>\n
To get the details about the ingress of the container of the related kubernetes cluster, there is a command similar to the command as:<\/p>\n
To get the list of all the ingress available on default namespace, run the command as shown below.<\/p>\n
$ kubectl get ingress<\/pre>\n
But to get the details of the specific ingress, you can enter the ingress name as:<\/p>\n
$ kubectl get ingress <ingress name><\/pre>\n
Example<\/strong>:<\/p>\n
$ kubectl get ingress ingress-nginx<\/pre>\n
<\/p>\n
Here, the ingress name is \u201cingress-nginx\u201d. It will display all the details regarding the specific ingress.<\/p>\n
Kubectl get configmap<\/h3>\n
To get the details about the configmap of the container of the related kubernetes cluster, there is a command similar to the command as:<\/p>\n
To get the list of all the configmap available on default namespace, run the command as shown below.<\/p>\n
$ kubectl get configmap<\/pre>\n
But to get the details of the specific configmap, you can enter the config name as:<\/p>\n
$ kubectl get configmap <configmap name><\/pre>\n
Example<\/strong>:<\/p>\n
$ kubectl get configmap nginx-http-cm<\/pre>\n
<\/p>\n
Here, the configmap name is \u201cnginx-http-cm\u201d. It will display all the details regarding the specific configmap.<\/p>\n
Kubectl get secrets<\/h3>\n
To get the details about the secrets of the container of the related kubernetes cluster, there is a command similar to the command as:<\/p>\n
To get the list of all the secrets available on default namespace, run the command as shown below.<\/p>\n
$ kubectl get secrets<\/pre>\n
But to get the details of the specific secrets, you can enter the secrets name as:<\/p>\n
$ kubectl get secrets <secrets name><\/pre>\n
Example<\/strong>:<\/p>\n
$ kubectl get secrets default-token-xct8s<\/pre>\n
<\/p>\n
Here, the secret name is \u201cdefault-token-xct8s\u201d. It will display all the details regarding the specific secrets.<\/p>\n
Kubectl get namespace<\/h3>\n
To get the details about the namespace of the container of the related kubernetes cluster, there is a command similar to the command as:<\/p>\n
$ kubectl get namespace <namespace name><\/pre>\n
Example<\/strong>:<\/p>\n
$ kubectl get namespace<\/pre>\n
<\/p>\n
Here, we are using the default namespace. By running the command as \u201ckubectl get namespace\u201d, we are listing all the available namespace.<\/p>\n
Conclusion<\/h2>\n
In this article, you have learnt how to use the \u201ckubectl get command\u201d with different options like pods, deployment, services, etc. It will fetch the related data on the cluster about the Kubernetes resources.<\/p>","protected":false},"excerpt":{"rendered":"
Kubernetes is an open-source platform that is the most portable for managing containerized workloads and services. It works as an automation tool by providing the services, support and…<\/p>","protected":false},"author":1,"featured_media":14977,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1,4,891,5,83,165,2],"tags":[901],"class_list":["post-14956","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-centos","category-debian","category-manjaro","category-mint","category-opensuse","category-red-hat","category-ubuntu","tag-kubectl-get"],"_links":{"self":[{"href":"https:\/\/linuxways.net\/de\/wp-json\/wp\/v2\/posts\/14956","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/linuxways.net\/de\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/linuxways.net\/de\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/linuxways.net\/de\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/linuxways.net\/de\/wp-json\/wp\/v2\/comments?post=14956"}],"version-history":[{"count":0,"href":"https:\/\/linuxways.net\/de\/wp-json\/wp\/v2\/posts\/14956\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/linuxways.net\/de\/wp-json\/wp\/v2\/media\/14977"}],"wp:attachment":[{"href":"https:\/\/linuxways.net\/de\/wp-json\/wp\/v2\/media?parent=14956"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/linuxways.net\/de\/wp-json\/wp\/v2\/categories?post=14956"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/linuxways.net\/de\/wp-json\/wp\/v2\/tags?post=14956"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}