EsmaeelE - Free Software enthusiast - Kubernetes

Kubectl Commands

2026-07-08T00:00:00+00:00

Kubectl Commands</h1>
Quick reference for common kubectl commands.</p>

Cluster Info</h2>

kubectl</span> cluster-info</span></span>
kubectl</span> get nodes</span></span>
kubectl</span> get namespaces</span></span></code></pre>Pods</h2>
kubectl</span> get pods -o wide</span></span>
kubectl</span> describe pod</span> <</span>pod-nam</span>e</span>></span></span>
kubectl</span> logs</span> <</span>pod-nam</span>e</span>></span> -f</span></span>
kubectl</span> exec -it</span> <</span>pod-nam</span>e</span>></span> -- /bin/sh</span></span>
kubectl</span> delete pod</span> <</span>pod-nam</span>e</span>></span></span></code></pre>Deployments</h2>
kubectl</span> get deployments</span></span>
kubectl</span> describe deployment</span> <</span>nam</span>e</span>></span></span>
kubectl</span> scale deployment</span> <</span>nam</span>e</span>></span> --replicas=3</span></span>
kubectl</span> rollout status deployment</span> <</span>nam</span>e</span>></span></span>
kubectl</span> rollout history deployment</span> <</span>nam</span>e</span>></span></span>
kubectl</span> rollout undo deployment</span> <</span>nam</span>e</span>></span></span></code></pre>Services</h2>
kubectl</span> get svc</span></span>
kubectl</span> describe svc</span> <</span>nam</span>e</span>></span></span>
kubectl</span> get endpoints</span> <</span>nam</span>e</span>></span></span></code></pre>Debugging</h2>
kubectl</span> get events --sort-by='.lastTimestamp'</span></span>
kubectl</span> top pods</span></span>
kubectl</span> top nodes</span></span>
kubectl</span> port-forward</span> <</span>pod-nam</span>e</span>></span> 8080:80</span></span></code></pre>Useful Aliases</h2>
alias</span> k</span>=</span>kubectl</span></span>
alias</span> kgp</span>=</span>'kubectl get pods'</span></span>
alias</span> kgs</span>=</span>'kubectl get svc'</span></span>
alias</span> kgd</span>=</span>'kubectl get deployments'</span></span>
alias</span> kd</span>=</span>'kubectl describe'</span></span>
alias</span> kx</span>=</span>'kubectl exec -it'</span></span></code></pre>



Kubernetes Lab Setup
2026-06-15T00:00:00+00:00
Kubernetes Lab Setup</h1>
Automated provisioning of an AWS EKS cluster for learning and testing.</p>
What it does</h2>

Provisions EKS cluster with Terraform</li>
Installs monitoring stack (Prometheus, Grafana)</li>
Configures ArgoCD for GitOps</li>
Includes sample application for testing</li>
</ul>
Tech Stack</h2>
Component</th> Tool</th></tr></thead>

IaC</td> Terraform</td></tr>
Containers</td> Kubernetes, Helm</td></tr>
CI/CD</td> ArgoCD</td></tr>
Monitoring</td> Prometheus, Grafana</td></tr>
</tbody></table>
Quick Start</h2>
terraform</span> init</span></span>
terraform</span> apply</span></span></code></pre>Links</h2>

GitHub Repo</a></li>
</ul>


Kubernetes Migration Lab: VMs to EKS
2025-11-10T00:00:00+00:00
This is a personal lab writeup, not a claimed production project.</strong> I set it up to practice the
workflow and tooling involved in a VM-to-Kubernetes migration, using a small sample service rather
than a real company's infrastructure.</p>
Goal</h2>
Get hands-on with the pieces that make up a typical Kubernetes migration, end to end:</p>

Provision an EKS cluster with Terraform</strong> instead of clicking through the AWS console.</li>
Package the service with Helm</strong> so config is versioned and repeatable.</li>
Wire up ArgoCD</strong> for GitOps-style deployment instead of manual kubectl apply</code>.</li>
Add Prometheus</strong> and Grafana</strong> for cluster and application metrics.</li>
Run the pipeline through GitHub Actions</strong> so image builds and Helm releases are automated.</li>
</ol>
What I practiced</h2>

Writing Terraform modules for VPC, subnets, and an EKS control plane, and tearing it down cleanly
afterward (terraform destroy</code>) to avoid runaway AWS costs on a personal account.</li>
Structuring a Helm chart with separate values</code> files per environment, and using helm diff</code> to
review changes before they hit the cluster.</li>
Pointing ArgoCD at a Git repo and watching it reconcile drift instead of trusting manual deploys.</li>
Setting resource requests/limits and a basic HorizontalPodAutoscaler, then load-testing to see
when pods actually scaled.</li>
Hooking up the kube-prometheus-stack and building a couple of Grafana dashboards for pod restarts
and request latency.</li>
</ul>
What I'd still want to test on a real workload</h2>

Zero-downtime cutover strategies (blue/green vs. canary) under real traffic, not synthetic load.</li>
Database migration alongside the app — stateful services are the part this lab skipped entirely.</li>
Cost comparison against the VM baseline with real numbers, not estimates.</li>
</ul>
Notes for next time</h2>
Terraform state management got messy once I started iterating quickly — next time I'd set up remote
state with locking from the start instead of retrofitting it. ArgoCD's health checks also needed
tuning for a custom readiness probe; the defaults reported "healthy" before the app was actually
ready to take traffic.</p>

Component</th>	Tool</th></tr></thead>
IaC</td>	Terraform</td></tr>
Containers</td>	Kubernetes, Helm</td></tr>
CI/CD</td>	ArgoCD</td></tr>
Monitoring</td>	Prometheus, Grafana</td></tr> </tbody></table> Quick Start</h2> terraform</span> init</span></span> terraform</span> apply</span></span></code></pre>Links</h2> GitHub Repo</a></li> </ul> Kubernetes Migration Lab: VMs to EKS 2025-11-10T00:00:00+00:00 This is a personal lab writeup, not a claimed production project.</strong> I set it up to practice the workflow and tooling involved in a VM-to-Kubernetes migration, using a small sample service rather than a real company's infrastructure.</p> Goal</h2> Get hands-on with the pieces that make up a typical Kubernetes migration, end to end:</p> Provision an EKS cluster with Terraform</strong> instead of clicking through the AWS console.</li> Package the service with Helm</strong> so config is versioned and repeatable.</li> Wire up ArgoCD</strong> for GitOps-style deployment instead of manual kubectl apply</code>.</li> Add Prometheus</strong> and Grafana</strong> for cluster and application metrics.</li> Run the pipeline through GitHub Actions</strong> so image builds and Helm releases are automated.</li> </ol> What I practiced</h2> Writing Terraform modules for VPC, subnets, and an EKS control plane, and tearing it down cleanly afterward (terraform destroy</code>) to avoid runaway AWS costs on a personal account.</li> Structuring a Helm chart with separate values</code> files per environment, and using helm diff</code> to review changes before they hit the cluster.</li> Pointing ArgoCD at a Git repo and watching it reconcile drift instead of trusting manual deploys.</li> Setting resource requests/limits and a basic HorizontalPodAutoscaler, then load-testing to see when pods actually scaled.</li> Hooking up the kube-prometheus-stack and building a couple of Grafana dashboards for pod restarts and request latency.</li> </ul> What I'd still want to test on a real workload</h2> Zero-downtime cutover strategies (blue/green vs. canary) under real traffic, not synthetic load.</li> Database migration alongside the app — stateful services are the part this lab skipped entirely.</li> Cost comparison against the VM baseline with real numbers, not estimates.</li> </ul> Notes for next time</h2> Terraform state management got messy once I started iterating quickly — next time I'd set up remote state with locking from the start instead of retrofitting it. ArgoCD's health checks also needed tuning for a custom readiness probe; the defaults reported "healthy" before the app was actually ready to take traffic.</p>

EsmaeelE - Free Software enthusiast - Kubernetes

Kubectl Commands

Kubectl Commands</h1> Quick reference for common kubectl commands.</p>

Kubernetes Lab Setup

Kubernetes Lab Setup</h1> Automated provisioning of an AWS EKS cluster for learning and testing.</p>

Kubernetes Migration Lab: VMs to EKS

Kubectl Commands</h1>
Quick reference for common kubectl commands.</p>

Kubernetes Lab Setup</h1>
Automated provisioning of an AWS EKS cluster for learning and testing.</p>