Leandro Dardick

Llegar a la meta no es vencer, lo importante es el camino y en el caer, levantarse, insistir y aprender

[Akhilesh Mishra @livingdevops]

The Kubernetes ecosystem is beautiful. Every tool exists to solve a problem that Kubernetes couldn't solve.

You run everything with kubectl. Get pods, describe, logs, exec, delete, apply, 50 times a day across 5 namespaces. It works, but it is slow and painful, specially -n namespcae in every command.

>> So you use K9s or Lens. A terminal UI that shows your entire cluster in one view. It lets you switch namespaces, different clusters, and tail logs, exec inside pod, and do everything you need.

You deploy with kubectl apply from your laptop. Someone changes a deployment directly on the cluster, and what is running no longer matches what is in Git. That is drift, and it is silent until prod breaks.

>> So you use ArgoCD. Git becomes the single source of truth, every change syncs to the cluster automatically, and if anyone touches a deployment manually ArgoCD overrides it back.

Your Kafka consumer has 200,000 messages piling up, CPU is at 5 percent, and HPA sees no reason to scale. The queue keeps growing, and users are waiting.

>> So you use KEDA. It scales pods on queue depth, SQS message count, or Prometheus metrics, and not just CPU. The backlog clears.

HPA adds pods during a spike, but the nodes are full, and new pods sit in Pending. HPA did its job, but the cluster had nowhere to put them.

>> So you use Karpenter. A new node appears in seconds when pods are stuck in Pending and disappears when the load drops. You only pay for what you use.

Every pod can talk to every other pod by default. Your payment service can reach your database, your internal tool can reach your logging service and nothing is blocked unless you block it.

>> So you use Network Policies. Your database only accepts traffic from the app, everything else is denied and the blast radius of a compromised pod shrinks dramatically.

You have 20 microservices, one starts responding slowly and retries pile up across 4 other services. A cascade begins and you have no visibility into where it started because all traffic is invisible.

>> So you use a Service Mesh. Istio or Linkerd puts a sidecar proxy next to every pod, gives you mTLS between every service, retries, circuit breaking and traffic metrics without touching a single line of app code.

Your secrets are Base64 encoded in Kubernetes, sitting in etcd and readable by anyone with kubectl access. You want them in Vault or AWS Secrets Manager but you do not want to rewrite your app to fetch them.

>> So you use the Secrets Store CSI Driver. Secrets live in Vault or AWS Secrets Manager and get mounted directly into your pod as files. The secret never lives in Kubernetes.

A developer ships a container running as root, another ships with no resource limits and you find out after the incident. Every time.
>> 𝘖𝘳𝘪𝘨𝘪𝘰𝘯𝘢𝘭 𝘱𝘰𝘴𝘵 𝘣𝘺 𝘈𝘬𝘩𝘪𝘭𝘦𝘴𝘩 𝘔𝘪𝘴𝘩𝘳𝘢

>> So you use Kyverno. Policies enforced at admission before anything enters the cluster, no root containers, no images without a digest and no deployments without limits.

Something is wrong. Pods are restarting, latency is spiking and memory is climbing but you have no numbers, no history and no way to know when it started.

>> So you use Prometheus and Grafana. Prometheus scrapes metrics from every pod, node and component and Grafana turns those numbers into dashboards. You see the spike, the exact time it started and which service caused it.

Grafana shows the spike but not which request triggered it, which service it hit first or where it slowed down. Logs give you fragments and metrics give you totals. Neither gives you the full story.

>> So you use Jaeger. It follows one request across every service it touches, shows you latency per hop and the exact failure point. The needle in the haystack, found in seconds.

That is the ecosystem. Not a list of tools.

[Alula @__alula]

the internet was supposed to be peer to peer, but in the CGNAT era people get excited when they can access their own devices over VPN

[IT Unprofessional @it_unprofession]

Last week I hosted family for Thanksgiving.

My 12-year-old nephew asked for the WiFi password.

He wanted to play Roblox on his iPad.

I looked at the device.

Unmanaged. No antivirus. No encryption.

I’m an IT Professional. I don't run an open network.

So I didn’t give him the password.

Instead, I spent 45 minutes provisioning a Guest VLAN.

I set up a captive portal.

I throttled the bandwidth down to 56kbps.

Then I blocked all traffic on ports 80 and 443.

He came back crying. He said it wouldn't load.

My sister screamed at me to "just let him play."

I told her that Zero Trust architecture doesn't care about bloodlines.

We didn't have a "fun" Thanksgiving.

But we had a secure perimeter.

You’re welcome for the compliance.

[Leandro Dardick @leandardick]

@fmendiguren El verano pasado fuimos a merendar 2 adultos y una nena de 3 años al Convento en Devoto, nos llevan ellos a una mesa grande porque era la unica libre y mientras estabamos sentados viendo la carta nos pidieron que liberemos la mesa porque llego un grupo que la necesitaba

[Scott Hanselman 🌮 @shanselman]

I run all of my DNS queries through a local LLM because it’s more deterministic

[Leandro Dardick @leandardick]

Driussi sos un hijo de puta

[Merill Fernando @merill]

iisreset

IYKYK

[ℏεsam @Hesamation]

"I use AI in a separate window. I don't enjoy Cursor or Windsurf, I can literally feel competence draining out of my fingers."

@dhh, the legendary programmer and creator of Ruby on Rails has the most beautiful and philosophical idea about what AI takes away from programmers.

[La Página Millonaria @RiverLPM]

ESTO es River. Escuchenló entero. ⚪🔴⚪

🎥 Tyc Sports

[Kai Lentit (e/xcel) @KaiLentit]

0.1x engineer [FULL]

[Aiden Bai @aidenybai]

hey guys i just learned this new git command for solving merge conficts

[Leandro Dardick @leandardick]

Kudos to the
@southworks
team for making this a reality. To the moon 🚀

[Satya Nadella @satyanadella]

3. Agent factory: Foundry is the complete app platform for building apps and agents. We are adding support for more models from Grok, Hugging Face, Meta, Mistral, and more. Plus: Agentic retrieval in Azure AI Search, Foundry Agent Service, integration with Copilot Studio, and more.

And we are ensuring the tools you already use for identity, management, and security will now all extend to agents too.

The NFL has already used Foundry, along with our data stack, to run its recent Combine.

[Manoj Ahirwar @manoj_ahi]

Got 1 paying user. Time to move to kubernetes.

[Leandro Dardick @leandardick]

@PeladoNerd Nos vemos alla!

[Kevin Naughton Jr. @KevinNaughtonJr]

levels in tech:
-junior eng
-mid level eng
-senior eng
-staff eng
-senior staff eng
-principal eng
-farmer

[Leandro Dardick @leandardick]

@nbellocam Extraño moment 🥹

[World of Engineering @engineers_feed]

2025 is a perfect square (45 times 45).

We will not see a year that is a perfect square until 2116.

[nixCraft 🐧 @nixcraft]

lol

[GitHub Projects Community @GithubProjects]

|￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣￣|
|Don'tPushToProductionOnChristmas|
|＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿＿|
\ (•◡•) /
\ /
——
| |
|_ |_