Tamal Saha

@diptanu @RonakNathani @ahmetb True. But the influencer / DevRel marketing from that time is still causing damage today.

@tsaha That was circa 2016. It wasn't good enough to run databases, by 2020 it was good IMO. We ran databases on K8s at LinkedIN. @RonakNathani and @ahmetb probably know more about this than me :D

It is funny to see Kubernetes go from "you should not run databases on Kubernetes" to "Kubernetes was built for ... databases that run forever."

@eastdakota @threepointone Go.

@threepointone What’s a good name?

rust is a terrible name for a programming language, almost as bad as javascript

🎉 We're thrilled to announce: .@KubeDB is now an official Red Hat .@OpenShift Certified Operator! This is a huge milestone for our team at AppsCode — and an even bigger win for OpenShift users who've been looking for a better way to run databases on Kubernetes. No more cloud lock-in. No more DIY overhead. Just a validated, Kubernetes-native DBaaS platform that works consistently across on-prem, cloud, ROSA, ARO, and air-gapped environments. Self-service for developers. Governance for platform teams. Any database, one control plane. 🚀 ✍️ Read the full story on the AppsCode Blog: appscode.com/blog/post/open… 📄 Joint Solution Brief: kubedb.com/solution-brief… 🔗 Red Hat Ecosystem Catalog: catalog.redhat.com/en/software/co… #KubeDB #RedHat #OpenShift #Kubernetes #DBaaS #CloudNative #KubernetesStorage #PlatformEngineering #AppsCode #RedHatSummit #RHSummit #Atlanta2026 #BetterTogether #Innovation #Database #TechCommunity

@alexellisuk @github @martinwoodward Not for cross org image push. That needs classic pat.

@tsaha @github @martinwoodward GHCR io supports short lived tokens minted from workflow permissions. Are you looking at something else?

Why not .@github .@martinwoodward ?

@github I have DM-ed you with the support ticket link.

@github can you help urgently. I have opened a ticket also.

🚀 Excited to announce our partnership with .@SUSE! SUSE Rancher Prime + .@KubeDB now delivers a true Kubernetes-native DBaaS — anywhere Kubernetes runs. ✅ No cloud lock-in ✅ Full data sovereignty (on-prem, hybrid, multi-cloud, edge, air-gapped) ✅ Automated provisioning, scaling, HA, backup & recovery ✅ Enterprise governance and self-service for developers Platform teams finally get consistent, governed database operations with complete control. Read the full story on the SUSE Blog: suse.com/c/dbaas-platfo… 👉 Download the joint solution flyer: kubedb.com/solutions-brie… #KubeDB #SUSE #RancherPrime #DBaaS #Kubernetes #DataSovereignty

🚨 Argo CD users have a serious problem. - Low-privilege users could read Kubernetes resources outside their app scope - ServerSideDiff=true made it worse - Plaintext Secrets could be exposed with zero redaction Affected: - 3.2 < v3.2.11 - 3.3 < v3.3.9 Fix: > Upgrade now > Disable ServerSideDiff=true > Tighten RBAC > Rotate Secrets if enabled This one is bad. github.com/argoproj/argo-…

6 years! But hey, better late than never. groups.google.com/a/kubernetes.i…

Starting June 1st, GitHub Copilot will move to a usage-based billing model as GitHub Copilot supports more agentic and advanced workflows. In early May, you'll see a preview bill experience, giving visibility into projected costs before the transition. 👉 Read more about the upcoming change: github.blog/news-insights/…

TL;DR: pgBackRest is no longer being maintained. For details see github.com/pgbackrest/pgb…

When this news broke I really wanted to understand how the linux scheduler work. So I started to research. What I gathered so far: (of course I might be missing something) Unlike user code, the Linux kernel code isn’t usually preemptable. That is when a system call is executed or a page fault is triggered the kernel runs to completion hogging the cpu core it runs on. The current Linux 7 tip experimenting a different preemption model for kernel code, so other more critical tasks can be scheduled. With this default mode, Postgres experienced 50% dropped in performance in one test suite 96 cores, with 100GB shared buffers pool. The theory from the thread discussion is that the large buffer pool 100 GB with the default 4kb kernel vm page size, caused significant number of page faults. Page faults gets triggered to allocate physical memory on first access or on swap (I have a video detailing this). Page fault runs kernel code to do the allocation of the physical memory and update the page table data structure for the process. If page faults are being preempted, it keeps the user process code in spin lock waiting for access. Indeed Andreas, the postgres maintainer, was able to prove that even with stable Linux you could see the contention obtaining memory from shared buffers, its just not as obvious with 7.0 where kernel preemption is enabled Using huge pages significantly reduces page faults, improving the performance. My Page Faults The Backend Engineering Show youtu.be/AsFxaZJ1M0k Phoronix article phoronix.com/news/Linux-7.0…

Upgraded .@claudeai from $20 to $200 plan on Friday. Today I left my laptop on with some online research. Came back 5 hours later with an email saying the account is suspended. WTF!

Kubernetes v1.36: ハル (Haru) - kubernetes.io/blog/2026/04/2… #Kubernetes

So, Elon has too much capacity or not enough?

The open source project that wins is the one that's just keeps plugging away.

"GitHub API rate limited (403), waiting 1m0s before retry" GitHub could just make that a paid product.

figma make needs a diff view