Ever typed ll a thousand times and forgot ls -la is the real command?
Aliases in Linux = your daily sanity saver.
From git status → gs to kubectl get pods → kgp – if you type it often, alias it.
DevOps life is just automating yourself out of a job, one alias at a time. #Linux
In Kubernetes, requests guarantee the minimum CPU/memory a container gets, while limits cap the maximum it can use.
Set requests too low → instability
Set limits too high → resource hogging
Balance is key for performance & efficiency
#Kubernetes#DevOps#CloudComputing
The write-ahead log (WAL) is both how databases commit fast and how they safely recover from crashes.
Outside of B-trees, it's probably the most important structure in Postgres and MySQL.
(it's called the "redo log" in MySQL-land)
Production Kubernetes cluster is down. Your manager is asking for updates every 5 minutes.
Here’s your step-by-step troubleshooting playbook:
Step 1: Get your bearings
Check where you are: kubectl config current-context
See all contexts: kubectl config get-contexts
Switch if needed: kubectl config use-context name
List namespaces: kubectl get ns
Step 2: See the big picture
Node health: kubectl get nodes
All pods: kubectl get pods -A
Recent events: kubectl get events –sort-by=.metadata.creationTimestamp -A
This tells you if it’s a cluster-wide issue or isolated problem.
Step 3: Focus on the failing pod
Get details: kubectl describe pod podname -n namespace
Check logs: kubectl logs podname -n namespace
Get inside: kubectl exec -it podname -n namespace – /bin/sh
Step 4: Check health probes
Look for probe failures in the describe output
Test probe endpoint: kubectl exec -it podname -n namespace – curl localhost:port/health
Step 5: Check deployments and rollouts
Rollout status: kubectl rollout status deployment/name -n namespace
View history: kubectl rollout history deployment/name -n namespace
Rollback: kubectl rollout undo deployment/name -n namespace
Step 6: Verify networking
List services: kubectl get svc -n namespace
Check endpoints: kubectl get endpoints -n namespace
Test DNS: kubectl exec -it podname – nslookup servicename
Step 7: Quick fixes that work
Restart deployment: kubectl rollout restart deployment/name -n namespace
Delete problematic pod: kubectl delete pod podname -n namespace
The key is following the steps in order, not jumping around randomly.
we just released 𝚙𝚘𝚜𝚝𝚐𝚛𝚎𝚜-𝚋𝚎𝚜𝚝-𝚙𝚛𝚊𝚌𝚝𝚒𝚌𝚎𝚜, inspired by Vercel's 𝚛𝚎𝚊𝚌𝚝-𝚋𝚎𝚜𝚝-𝚙𝚛𝚊𝚌𝚝𝚒𝚌𝚎𝚜
these are the Agent Skills that we use on the supabase platform - including performance, security, & schema design
details ↓
https://t.co/7GOYpuin6e
Amazon confirms fresh "connectivity issues" following a massive outage that disrupted several popular websites and apps. Follow live updates.
https://t.co/yrzMctskiB