Kubectl - Command

kubectl run mini-kube  // is used to deploy an application on the cluster

kubectl cluster-info // command to view information about the cluster

kubectl get nodes // get the information about all the nodes in the cluster


kubectl get pods -o custom-columns="NAME:.metadata.name,IMAGE:.spec.containers[*].image,STATUS:.status.phase,NODE:.spec.nodeName"

NAME          IMAGE           STATUS    NODE

nginx-pod     nginx:alpine    Running   worker-1

redis-pod     redis:7         Running   worker-2


kubectl get pods -o custom-columns="\

NAMESPACE:.metadata.namespace,\

NAME:.metadata.name,\

IMAGE:.spec.containers[*].image,\

READY:.status.containerStatuses[*].ready,\

RESTARTS:.status.containerStatuses[*].restartCount,\

STATUS:.status.phase,\

NODE:.spec.nodeName,\

POD_IP:.status.podIP,\

AGE:.metadata.creationTimestamp"

OUTPUT BELOW: 

NAMESPACE  NAME        IMAGE        READY   RESTARTS  STATUS       NODE       POD_IP       AGE

default         nginx-pod   nginx:alpine             true                    0         Running    worker-1   10.1.2.3                2d  


SERVICE

kubectl get svc -o custom-columns="\

NAMESPACE:.metadata.namespace,\

NAME:.metadata.name,\

TYPE:.spec.type,\

CLUSTER-IP:.spec.clusterIP,\

EXTERNAL-IP:.status.loadBalancer.ingress[*].ip,\

PORTS:.spec.ports[*].port,\

TARGET-PORTS:.spec.ports[*].targetPort,\

SELECTOR:.spec.selector"


DEPLOYMENT

kubectl get deploy -o custom-columns="\

NAMESPACE:.metadata.namespace,\

NAME:.metadata.name,\

READY:.status.readyReplicas,\

UP-TO-DATE:.status.updatedReplicas,\

AVAILABLE:.status.availableReplicas,\

REPLICAS:.spec.replicas,\

IMAGE:.spec.template.spec.containers[*].image,\

STRATEGY:.spec.strategy.type,\

AGE:.metadata.creationTimestamp"


CONFIG MAPS

kubectl get configmap -o custom-columns="\

NAMESPACE:.metadata.namespace,\

NAME:.metadata.name,\

DATA-KEYS:.data,\

CREATION-TIME:.metadata.creationTimestamp"

The below tells you what version to use

kubectl explain replicaset 

kubectl explain deployment

KIND: Deployment
VERSION: apps/v1

DESCRIPTION:
Deployment enables declarative updates for Pods and ReplicaSets.

FIELDS:
apiVersion <string>
APIVersion defines the versioned schema of this representation of an object.

kubectl get all  // to see all the created components


. Show current context name -- which namespace you currently are in

kubectl config current-context

kubectl get pods --all-namespaces


kubectl api-resources 

NAMESHORTNAMESAPIVERSIONNAMESPACEDKINDPurpose
bindings—v1trueBindingBinds a Pod to a Node
componentstatusescsv1falseComponentStatusHealth of control plane components
configmapscmv1trueConfigMapStore non-sensitive configuration
endpointsepv1trueEndpointsBackend Pod IPs for Services
eventsevv1trueEventCluster activity logs/events
limitrangeslimitsv1trueLimitRangeResource limits in namespace
namespacesnsv1falseNamespaceLogical cluster isolation
nodesnov1falseNodeWorker/master machines
persistentvolumeclaimspvcv1truePersistentVolumeClaimRequest storage
persistentvolumespvv1falsePersistentVolumeActual storage resource
podspov1truePodSmallest deployable unit
podtemplates—v1truePodTemplateTemplate for Pod creation
replicationcontrollersrcv1trueReplicationControllerLegacy Pod replica manager
resourcequotasquotav1trueResourceQuotaNamespace resource restrictions
secrets—v1trueSecretStore sensitive data
serviceaccountssav1trueServiceAccountIdentity for Pods
servicessvcv1trueServiceStable networking endpoint


Comments

Post a Comment

Popular posts from this blog

Azure Migrate

Image
 Azure Site Recovery an earlier tool for migration: Thought purpose built for Disaster Recovery ASR: Azure Site Recovery Yes — Azure Site Recovery (ASR) is commonly used as a migration tool , even though its primary purpose is disaster recovery. How ASR Is Used for Migration Organizations use ASR to perform: Lift-and-shift migrations VMware to Azure migrations Hyper-V to Azure migrations Physical server to Azure migrations ASR replicates workloads continuously from on-premises infrastructure to Azure. During the final cutover, the replicated VM is started in Azure with minimal downtime. Migration Workflow Using ASR Typical Flow Discover on-prem servers Enable replication Continuous data synchronization Test failover (optional) Planned failover/cutover Azure VM becomes production workload This approach minimizes: Downtime Data loss Manual rebuild effort Why ASR Is Popular for Migration ASR vs Azure Migrate Real-World Use Case Example: Company has 200 VMware VMs on-premises. The...
Read more

Azure -- All Networking Components

   1. Virtual Network (VNet) 📌 One-paragraph explanation A Virtual Network (VNet) is the core private networking space in Azure where all cloud resources communicate securely. It is used to isolate workloads, control IP ranges, and create a private environment similar to a traditional data center network but fully software-defined in the cloud. 🔍 Details Where used: Hosting VMs, AKS clusters, databases, internal services Connected services: VM, Load Balancer, Application Gateway, Azure Firewall, Private Endpoint Dependencies: None (foundation component) Purpose in architecture: Acts as the main “network boundary” for all resources 🧩 2. Subnet 📌 One-paragraph explanation A subnet is used to divide a VNet into smaller logical networks so that different layers of an application (web, app, database) can be separated and controlled independently for security and traffic management. 🔍 Details Where used: Tiered architectures (web/app/db layers), microse...
Read more

All Kuberneters - Components

  Kubernetes Core Resources Explained 1. Pods What It Is A Pod is the smallest deployable unit in Kubernetes. It contains one or more containers that share: Network Storage Lifecycle Used For Running application containers Grouping tightly coupled containers together Example A web application container running inside a pod. 2. Deployments What It Is A Deployment manages Pods and ReplicaSets. Used For Rolling updates Application version upgrades Scaling applications Self-healing applications Example Deploying 3 replicas of an NGINX application. 3. ReplicaSets What It Is A ReplicaSet ensures a specified number of pod replicas are always running. Used For High availability Maintaining desired pod count Example Keeping 5 backend pods running at all times. 4. DaemonSets What It Is A DaemonSet ensures one pod runs on every node (or selected nodes). Used For Monitoring agents Log collectors Security agents Example Running Fluentd or Prometheus Node Exporter on all nodes. 5. StatefulSets W...
Read more