Amit Jha

Passionate about AWS Cloud ☁️, DevOps ⚙️, and Java DSA enthusiast 📚. Always learning and exploring new technologies. #AWS #DevOps #Java #DSA #AIML''

[Mrinal @Hi_Mrinal]

Found a GOATED read on internals of Postgres

https://t.co/VrQhMg2i56

[Priyanka Vergadia @pvergadia]

This video literally explains AI Agents in 19 minutes.

[LearnKube @learnk8s]

This case study explains how the team at Beekeeper by LumApps adopted Karpenter on their Amazon EKS clusters

It shares real-world lessons around AMI drift, node disruption budgets and scaling flexibility

➤ https://t.co/iPIJLWYolT

[ℏεsam @Hesamation]

bro casually walks and explains 5 GPU performance optimization methods for LLMs. one of the most simple and intuitive explanations for beginners.

[Amit Jha @Amit01_TX]

Literally Nailed it.

[BhikuMhatre @MumbaichaDon]

You nailed it, Bro 👏👏👏

That last statement 🫡

[BhikuMhatre @MumbaichaDon]

You nailed it, Bro 👏👏👏

That last statement 🫡

[Tom Dörr @tom_doerr]

Analyzes traffic for Kubernetes with packet inspection

https://t.co/UFzRD3nnbn

[Amazon Web Services @awscloud]

Happy New Year! 🎆
┏━━┓┏━━┓┏━━┓┏━━┓
┗━┓┃┃┏┓┃┗━┓┃┃┏━┛
┏━┛┃┃┃┃┃┏━┛┃┃┗━┓
┃┏━┛┃┃┃┃┃┏━┛┃┏┓┃
┃┗━┓┃┗┛┃┃┗━┓┃┗┛┃
┗━━┛┗━━┛┗━━┛┗━━┛

[FearBuck @FearedBuck]

2026 will be elite

[Kube Architect @K8sArchitect]

MOCO provides a reliable and efficient way to deploy, manage, and maintain MySQL databases in a containerized environment

MOCO supports GTID-based semi-synchronous replication, ensuring high availability and data consistency

➜ https://t.co/C77rSopczm

[Kube Architect @K8sArchitect]

Karpor is a tool that brings advanced Search, Insight, and AI capabilities to Kubernetes, providing crucial visibility into Kubernetes clusters across any cloud

➜ https://t.co/XOT4sQlzHT

[Kube Architect @K8sArchitect]

NGINX Gateway Fabric is an open-source project that implements the Gateway API using NGINX as the data plane

The goal of this project is to implement the core Gateway APIs

➤ https://t.co/TqkyHbUA6J

[Kubezilla @kubezilla_io]

What's new in K8sGPT? AI-powered diagnostics for your Kubernetes clusters—in plain English.

@kubetools #Kubernetes #AI #K8s

https://t.co/qKANwXvPQF

[Manly Mentor @manly_mentor]

Men,
This is why you Must dream big ‼️

[The AI Investor @The_AI_Investor]

Listen to Elon explaining first-principles thinking process.

[Immanuel @immanuel_vibe]

⚡️ How to enhance Argo CD performance - tips from production

Bump up `ARGOCD_RECONCILIATION_TIMEOUT` and tune `--status-processors` / `--operation-processors` based on your cluster count - defaults are way too conservative for 500+ apps

Enable manifest caching with `reposerver.enable.git.submodule=false` if you don't need submodules - saves a ton of git overhead

Shard your application controller across multiple replicas using `--sharding-method=round-robin` and set proper `ARGOCD_CONTROLLER_REPLICAS`

Disable resource health checks for CRDs you don't care about via `https://t.co/wxhCZ1svHv` - watching everything is a CPU killer

Use ApplicationSets with progressive syncs instead of deploying hundreds of individual apps - way less memory pressure on the controller

Set `REDIS_RETRY_COUNT=5` and configure proper connection pooling - Redis timeouts under load are the silent killer

If you're hitting repo-server bottlenecks, add more replicas AND increase `ARGOCD_EXEC_TIMEOUT` for those chunky Helm charts with 100+ templates.

#argo_cd #gitops #ci_cd #docker #kubernetes #devops #k8s #cloud #sre

[LearnKube @learnk8s]

SharedVolume is a Kubernetes operator that lets you sync data from sources like Git, S3, HTTP or SSH and make it available as a shared volume across pods via annotations

➜ https://t.co/ZQiL7VpSWY

[TechOps Examples @techopsexamples]

25 Blogs to Learn 25 Kubernetes Concepts:

1) Kubernetes Architecture: https://t.co/GQpHJILbKg
2) POD Lifecycle: https://t.co/dNBFn3whNE
3) etcd Setup: https://t.co/u2r0kmrOeM
4) etcd Locks: https://t.co/S6w9G1UqvC
5) crashloopbackoff: https://t.co/t7x3FLyj1y
6) OOMKilled: https://t.co/cREbsUHVyS
7) ImagePullBackOff: https://t.co/HpW4Fit2Wf
8) CreateContainerConfigError: https://t.co/0tIPZwpQ9C
9) CreateContainerError: https://t.co/AYL8eekbn8
10) RunContainerError: https://t.co/xa104gOwOj
11) Node Disk Pressure: https://t.co/VFWIQDzCQ0
12) Node Not Ready:https://t.co/AxBkdK2qpY
13) Pod Disruption Budget: https://t.co/g1IGnB1r2P
14) RBAC: https://t.co/4Bsg1Q2BkV
15) DNS Optimization: https://t.co/WhZwUAvffv
16) Kubernetes Controller: https://t.co/NuXY0WPNDm
17) pod.yaml Breakdown: https://t.co/sLWQhRWvFc
18) Kubernetes Upgrades: https://t.co/YlHrQ3sqZc
19) KEDA vs Karpenter: https://t.co/Zt9mDGKykn
20) Operator vs Helm: https://t.co/sFlISE7TRA
21) Kubernetes Air Gap: https://t.co/u3dgGHAwY2
22) QoS Classes: https://t.co/jtliOiq0IO
23) Kubernetes CI/CD: https://t.co/DPxGh3TGyW
24) Deployment Strategies: https://t.co/HrEhY1j3VC
25) Security Contexts: https://t.co/OMPX6J3gMa

58K+ read our free newsletter: https://t.co/wwkI6UOSo4

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

🔁 Consider a repost if this is helpful.

[LearnKube @learnk8s]

Kubetail is a bash script that enables you to aggregate (tail/follow) logs from multiple pods into one stream

This is equivalent to running `kubectl logs -f`, but for multiple pods

➜ https://t.co/MEPjp48JYy

[Eduardo Borges @duborges]

i've been hacked

and traced the malware's wallet to see how much money they actually made from this new exploit

(if you use Next.js/React, READ THIS!)

I woke up to a terrifying email from Hetzner: "Netscan Detected."

my server was blocked and a botnet was using my IP to attack others

i dug into the logs and what I found the anatomy of the attack:

1) The Symptoms: I logged into htop and saw the mess:

- CPU usage: 361%
- A process named ./3ZU1yLK4 running wild
- Random connections to an IP in the Netherlands

my server wasn't serving my app anymore; it was mining crypto for someone else!

2) The Culprit: It wasn't a random SSH brute force. It was inside my Next.js container

the malware was sophisticated

it renamed itself nginxs and apaches to look like web servers

it even had a "killer" script that hunted down other hackers' miners to kill the competition

3) The "Root" Cause (literally): Probably the recent React/Next.js CVE-2025-66478 exploit was the entry point

(my project was running on "next": "15.5.4", behind cloudflare dns, but their recent fix didn't work apparently)

but the fatal error was mine: my Docker container was running as ROOT

Coolify deploys like this automatically when using Nixpacks, and I never changed it...

so because of USER root, the malware could install cron, systemd, and persistence scripts to survive reboots

meaning, it was able to infect my whole server, from a single Next.js docker!

4) The Forensics: I ran docker diff on the container - the hacker didn't just run a script, they installed a whole toolset..

- /tmp/apaches.sh (The installer)
- /var/spool/cron/root (The persistence)
- /c.json (The wallet config)

5) The Fix: I killed the container, scrubbed the host, and extracted the malware for analysis.

but the real fix is in the Dockerfile. if you are deploying Node/Next.js, DO NOT use the default (root), you must:

- RUN adduser --system nextjs
- USER nextjs

if you have Docker on ROOT and didn't update the exploited react version, you'll be hacked soon

check your containers NOW. Run: docker exec <container_id> id

(or get the full list first: docker stats --no-stream)

If it says uid=0(root), you are one vulnerability away from being a crypto-miner host.

(it's easy to notice when hacked, it will be a command running on the top CPU%, using all your hardware resources)

6) The Money: I dug deeper and recovered the config file (c.json)

- Wallet: A Monero (XMR) address: 831abXJn8dBdVe5nZ***
- Pool: auto.c3pool . org

and ofc i tracked the hacker’s wallet on the mining pool

7) The Scale: My server wasn't alone. It was just 1 of 415 active zombies in this botnet

they are burning the CPU of 400+ cloud servers... to earn...

guess how many millions?

$4.26/day

on the image attached you can see: "Total Paid: 0.00", meaning this campaign just started. I caught them on Day 1.

i also tracked back the server where they hosted the malware, and by inspecting the code, I found several comments in Chinese, so I guess that's their origin

im rebuilding from scratch on a fresh VPS. the lesson was expensive, but at least I caught it before the hosting nuked my account permanently...

PS: I have the IP for all the other machines mining with that malware, not sure how I can help them, but feel free to contact me if ur doing infosec

stay safe