Hayden 🕊️

L'ombre de la mort plane sur le navire mais je monte à bord

[Branko @brankopetric00]

6 years of Kubernetes and I still ask AI how to get logs from the previous container.

[𝐍𝐨𝐚𝐡 @noahelhadedy]

7 Mockup tools every designer should bookmark.

1. https://t.co/jHKT3e5vLT
2. https://t.co/UURNQaJlFu
3. https://t.co/HJblChzBBI
4. https://t.co/iildz4sIn3
5. https://t.co/ffAKosGldP
6. https://t.co/TTmvKdwDqS
7. https://t.co/Njd0R8QE9p

What did I miss?

[h16 @_h16]

Un abonnement à 200$ sur Claude, un prompt malin et une orchestration bien pensée et voilà quelques problèmes mathématiques et cryptographiques résolus...

Et on n'est encore qu'au début de l'exponentielle...

[Calcifer @jsuiscooltkt]

Des fois je repense au mec que j’ai rencontré pendant le salon d’orientation en 2018 et qui m’a vendu l’expertise comptable comme le Graal mdrrr sale batard t’as niqué ma vie

[Himanshu Hingorani @himanshubuildss]

The best design inspiration sites you need to save 🔖

1. https://t.co/RlChWqggj8 - 600+ award-winning prompts with full source code for 3D and scroll-driven sites.
2. https://t.co/75zV2ioDNu - navbar inspiration
3. https://t.co/XPn2VgZBdJ - better footers
4. https://t.co/NDaj9DThhe - CTA inspiration
5. https://t.co/iRLY9tbhpW - Clean, minimal websites.
6. https://t.co/SuP8k1gYRC - Mobile UI animations & interactions.
7. https://t.co/E1Guwfthj7 - UI concepts and challenges.
8. https://t.co/mKNaYCzVDC - Social media visuals.
9. https://t.co/XPn2VgZBdJ - Creative footer examples.
10. https://t.co/OLdDWF3wTb - Landing page references.

What did I miss? 👀

[Saurav Chaudhary @sauravstwt]

Senior SRE Interview at Cloudflare

Round 1: Systems Design
• Design a global anycast network that keeps serving when an entire data center disappears.
• How would you roll out a config change to 300+ edge locations safely?
• Design a DDoS mitigation pipeline that drops attack traffic without dropping legitimate users.
• How do you manage BGP changes safely? What guardrails prevent a bad route announcement?
• How would you design a canary system for edge software where traffic differs by region?

Round 2: RCA & Troubleshooting
• A single regex deployed globally pegs CPU on every edge node at once. How do you find it and stop the bleeding?
• 5xx errors spike for one ASN only. Walk me through your debugging path.
• DNS resolution is slow, but the authoritative servers look healthy. Where is the problem?
• A kernel upgrade rolled to 10% of fleet and packet drops appear. How do you isolate the cause?
• Your dashboards are down during the incident. How do you debug without them?

Round 3: Leadership & Judgement
• You have to roll back a global change, but the rollback itself is risky. How do you decide?
• Walk me through how you write a blameless postmortem for an outage that hit millions of sites.
• How do you balance shipping speed against blast radius?
• How do you communicate publicly during an active incident?

💡 TL;DR: If you haven't:
1. Designed safe global rollouts with staged blast radius
2. Debugged network and DNS issues below the application layer
3. Handled an incident with observability partially down
4. Written postmortems that changed the system, not just the wording
Then Cloudflare interviews won't just test you; they'll expose the cracks in your production mindset. But what if you could train on this before getting grilled?

🚨 That's why I help engineers prepare for these interviews before they face the real pressure. We work on production thinking, troubleshooting, architecture, and how you explain your decisions.

If you want to train with me 1:1, fill out the form below. Tell me where you're stuck, and I'll help you close the gaps.
🔗 https://t.co/DG1l31TbMN

[Akhilesh Mishra @livingdevops]

Kubernetes troubleshooting guide for beginners

Kubernetes troubleshooting is not about knowing commands. It is about knowing where to look.

Here is how I think through k8s troubleshooting, and it has worked almost every time.

1. The first thing I do is stop assuming.

- kubectl get pods showing Running means nothing.
- A pod can be running, and your app can still be broken inside.
- Running means the container process has started. That is it.

2. The second thing I do is separate the layers.

- Is the problem at the node level?
- Is it at the pod level?
- Is it at the container level?
- Is it at the volume level?
- Is it at the network level?

-- Each layer has different failure modes.
-- Each layer has different signals.
-- Events tell you what Kubernetes tried to do.
-- Logs tell you what your app did.
-- You need both. But in that order.

>> Node level first.

- kubectl get nodes -> Are all nodes Ready?
- kubectl describe node -> check for MemoryPressure, DiskPressure, PIDPressure.
- If the node is unstable, everything running on top of it lies to you.

>> Then pod level.

- kubectl get pods is not enough.
- kubectl describe pod is where the real story is.
- Go straight to the Events section at the bottom. That section tells you exactly what Kubernetes tried and where it failed.

-> FailedMount means volume problem.
-> FailedScheduling means node problem.
-> CrashLoopBackOff means the container is dying on startup.

If you skip Events, you are debugging blind.

>> Then container level.

- A container can be running and still be broken.
- Liveness probe passing does not mean the app is healthy.
- It means one endpoint returned 200.

kubectl exec into the pod and test the actual business logic.

-> Hit the real endpoint.
-> Check your database connection.
-> Check your downstream APIs.

If your readiness probe checks /health but your app depends on /payment, those are two different realities.

>> Then volume level.

-> If your pod is stuck in Pending, run kubectl describe pod and look for a Multi-Attach error.
-> This means a volume is still locked to a terminated node.
-> The new pod cannot claim it.
-> You have to manually clean up the stale attachment before the pod can start.

Storage issues are silent blockers.

Depending on your storage backend (e.g., AWS EBS or other CSI drivers), this may require manual cleanup or may resolve automatically.

>> Then network level.

kubectl get svc -> is the service correctly defined?
kubectl describe svc -> are endpoints mapped to the right pods?

Then get inside the pod and run curl and nslookup against your service name.

Common failures here are the selector not matching pods, the wrong targetPort, and CoreDNS not resolving correctly.

If requests are failing intermittently with no clear pattern, network and readiness together are usually the culprit.

>> Then check your probes.

- An initialDelaySeconds too low means Kubernetes marks a pod ready before the app actually is.
- A slow-starting app with a 10-second readiness probe will pass the check and start receiving traffic before its connection pool is initialized.
- 1 in 50 requests will fail. No clear error. Hours of confusion.
- Always test your readiness probe against the real path your app uses in production.
- Not just a /health endpoint that always returns 200.

TLDR;

While troubleshooting Kubernetes issues, follow this pattern

Node → Pod → Container → Volume → Network

AND

- Don't assume Running means healthy.
- Read Events before you read logs.
- Never trust a health check that doesn't test real business logic.

I hope it helps Kubernetes beginners.

[BMS | Shadow @ShadowYgo]

J’aime trop bosser avec les italiens parce qu’ils ont un esprit de vendetta pour RIEN.

Y’a un collègue là j’ai du l’impliquer dans un projet qui lui casse les couilles et la première question qu’il me pose c’est « qui t’as donné mon nom déjà ? »

[Programmer Humor @PR0GRAMMERHUM0R]

The middle of the curve has spent a year building the orchestration layer. The code is still not written.

[Everything Metal Gear ❗ @MetalGear_QWC]

Metal Gear Solid 2: Sons of Liberty (2001)
Art by Yoji Shinkawa

[Tech Fusionist | Kushal Gangil @techyoutbe]

How do Kubernetes experts debug production issues? 👇

Not by randomly restarting pods or chasing dashboards.

They follow 4 rules:
→ Start with impact
→ Narrow by elimination
→ Correlate signals
→ Document the root cause

And 2 patterns:
→ Hypothesis-driven debugging
→ Reduce the blast radius

Systematic debugging beats heroics every time.
Save this for your next Kubernetes incident. 🔖

[Zsolt Kacso @kaolti]

Playing with some elemental cards.

[🧃Вовчик🧃 @xkaiju10x]

1. Au moins ça me permet de me rendre compte que l'informatique est vraiment plus un domaine qui me passionne... wow. Je suis tellement paumé dans ma life, j'ai aucune vraie passion, aucun but précis. Ma seul motivation de continuer en info est financière.

[Ayaan 🐧 @twtayaan]

Somewhere along the way, deploy became a full time job.

[Yoshik @AskYoshik]

Dear DevOps engineers,

How many of these skills are on your CV?

1. Linux - Processes, systemd, permissions, memory, disk
2. Networking - DNS, TCP/IP, routing, NAT, TLS, proxies
3. Containers - Docker, containerd
4. Kubernetes - Pods, Services, Ingress, Helm, probes, autoscaling
5. CI/CD - Jenkins, GitHub Actions, GitLab CI, Argo CD
6. Infrastructure as Code - Terraform, OpenTofu, Pulumi
7. Automation - Ansible, SaltStack, Bash, Python
8. Cloud - AWS, GCP, Azure
9. Observability - Prometheus, Grafana, Loki, OpenTelemetry
10. Logging - ELK/OpenSearch, Fluent Bit
11. Databases - Postgres, MySQL, Redis
12. Messaging - Kafka, RabbitMQ, NATS
13. Load Balancing - Nginx, HAProxy, ALB
14. Security - IAM, secrets, RBAC, WAF
15. Reliability - SLOs, alerts, incident response, postmortems
16. Debugging - logs, metrics, tcpdump, strace, dig, curl
17. System Design - scaling, caching, queues, failover, tradeoffs

[TechOps Examples @techopsexamples]

Kubernetes skills are still some of the highest paid tech skills in 2026.

These 7 practical Kubernetes troubleshooting use cases are worth saving:

1: // How To Fix Kubernetes Node Not Ready
↳ https://t.co/AxBkdK2qpY

2: // How to Fix Kubernetes Node Disk Pressure
↳ https://t.co/VFWIQDzCQ0

3: // Understanding Kubernetes CreateContainerError
↳ https://t.co/AYL8eekbn8

4: // Understanding Kubernetes CreateContainerConfigError
↳ https://t.co/0tIPZwpQ9C

5: // Understanding Kubernetes ImagePullBackOff
↳ https://t.co/HpW4Fit2Wf

6: // Understanding Kubernetes RunContainerError
↳ https://t.co/xa104gOwOj

7: // Understanding Kubernetes OOMKilled
↳ https://t.co/QmCBxkiSOe

Save this list. It'll save you hours and help to get 10x better at practical Kubernetes.

--
P.S. 50K+ read my DevOps and Cloud newsletter: https://t.co/wwkI6UOSo4

What do we cover:
DevOps, Cloud, Kubernetes, IaC, GitOps, MLOps

🔁 Consider a Repost if this is helpful

[Webologie @Webologie_me]

Des messages qui traversent l'Île-de-France sans antenne relais, sans internet et sans opérateur. Juste des petits boîtiers radio à quelques dizaines d'euros, qui se relaient entre eux.
MeshCore, c'est le cousin de Meshtastic : même technologie radio LoRa, même type de boîtier, mais une autre organisation du réseau, avec des répéteurs fixes placés en hauteur. Les deux ne se parlent pas entre eux, il faut choisir son camp.
Le jour où le réseau mobile tombe, ceux qui ont ce genre de boîtier dans un tiroir continueront à échanger. Les autres attendront.
Le guide complet gratuit comme d'hab, est en commentaire 👇

[Techopse @techopse]

The World You Grew Up in No Longer Exists.

[Webologie @Webologie_me]

GitHub fait peur à beaucoup de monde. Pourtant, pour télécharger un logiciel, vous n'avez besoin de comprendre que trois choses.

GitHub, c'est une immense bibliothèque où les développeurs publient le code de leurs logiciels, à la vue de tous. Chaque page s'appelle un « dépôt » : c'est la vitrine d'un projet. Le code est public, donc n'importe qui peut vérifier ce que fait le logiciel. C'est pour ça qu'on le croise partout dès qu'on parle d'open source.

Pour télécharger, ignorez le gros bouton vert « Code ». Il donne le code brut, pas un programme prêt à installer. Regardez plutôt à droite de la page, la rubrique « Releases ». Ce sont les versions officielles. Cliquez sur la plus récente et prenez le fichier qui correspond à votre appareil : .exe pour Windows, .dmg pour Mac, .apk pour Android.

Le piège, maintenant. En 2024, des chercheurs de Check Point ont découvert plus de 3 000 faux comptes qui distribuaient des étoiles à des dépôts piégés pour les faire paraître fiables. Ces dépôts cachaient des logiciels voleurs de mots de passe.
Ma règle est simple : je n'arrive jamais sur GitHub par une recherche. Je pars toujours du site officiel du projet et je clique sur son lien GitHub.

Et vous, GitHub vous a déjà fait renoncer à installer un logiciel ?