Davanum Srinivas (@dims)

Davanum Srinivas (@dims)

@dims.dev

#OpenSource Person, Principal Engineer for Nvidia. He/Him.

3.2K followers3.9K following600 posts

Davanum Srinivas (@dims) reposted

Tim Hockin
@thock.in

Every post on /r/kubernetes which concludes with "Curious to hear..." will continue to be removed with prejudice. Just stop with the BS, please.

Davanum Srinivas (@dims) reposted

Damon Cortesi
@dacort.velocipig.com

'Maybe next KubeCon needs a "Boring But Critical Infrastructure" track.' www.distributedthoughts.org/while-everyo... I'd attend that @ironyuppie.com

distributedthoughts.orgTwo KubeCons, One Conference: While Everyone Demos AI Agents, Engineers Are Fighting With SyslogsKubeCon North America 2025 was actually two different events happening simultaneously in the same building. The first KubeCon lived on the exhibit floor. Every third booth featured some variation of ...

Davanum Srinivas (@dims) reposted

James Strong
@strongjz.bsky.social

If you missed our talked, We have a post on #kubernetes blog discussing the plans to archive Ingress-nginx - Project is getting archived in March 2026 - No dependency updates, bug fixes, releases - Images available, Helm charts - Not gonna break deployments www.kubernetes.dev/blog/2025/11...

kubernetes.devIngress NGINX Retirement: What You Need to KnowTo prioritize the safety and security of the ecosystem, Kubernetes SIG Network and the Security Response Committee are announcing the upcoming retirement of Ingress NGINX. Best-effort maintenance will...
James Strong@strongjz.bsky.social

I'll be speaking #kubecon Wednesday about "To InGate and Beyond Ingress-nginx! - James Strong & Marco Ebert" at KubeCon + CloudNativeCon North America 2025. sched.co/27No6.

sched.coKubeCon + CloudNativeCon North America 2025: To InGate and Beyond Ingress-nginx! - Ja...View more about this event at KubeCon + CloudNativeCon North America 2025

Davanum Srinivas (@dims) reposted

Micah Hausler
@micahhausler.com

This is a truly significant announcement for organizations who want to know that Amazon EKS is secure to run their most sensitive workloads. aws.amazon.com/blogs/securi...

aws.amazon.comAmazon Elastic Kubernetes Service gets independent affirmation of its zero operator access design | Amazon Web ServicesToday, we’re excited to announce the Amazon Elastic Kubernetes Service (Amazon EKS) zero operator access posture. Because security is our top priority at Amazon Web Services (AWS), we designed an oper...
Davanum Srinivas (@dims)
@dims.dev

i had a blast! thanks @johncodes.com

John McBride@johncodes.com

🎙️Had the chance to sit down with @dims.dev to discuss the cloud native ecosystem, the health of the Kubernetes project, and Kubernetes as the AI platform of the future. One the cloud native people won't want to miss! www.heavybit.com/library/podc...

heavybit.comOpen Source Ready | Ep. #23, Kubernetes, AI, and Community Engagement with Davanum Srinivas | HeavybitIn episode 23 of Open Source Ready, Brian and John sit down with Davanum “Dims” Srinivas to discuss the health and future of the Kubernetes community.

Davanum Srinivas (@dims) reposted

Rachel Stephens
@rstephens.me

A beautiful #monktoberfest metaphor woven by @juliaferraioli.com about the cost and weight of carrying forks: "Forks are not universally bad. They happen because of an unmet need. We need forks because we needed agency that upstream did not allow us."

Davanum Srinivas (@dims) reposted

paris.
@parisinbmore.bsky.social

stellar human gone too soon. i’ll always remember his joy at KubeCons even during booth duty. kubernetes community has many fond memories of Han. And as Solly says in the thread: > may his memory be a blessing to you as it is to me. (and hit that gofundme link for the fam)

Solly@directxman12.dev

my friend han passed away earlier this week www.legacy.com/us/obituarie...

legacy.comHan Kang Obituary (1983 - 2025) - Legacy RemembersView Han Samuel Kang's obituary, send flowers and sign the guestbook.

Davanum Srinivas (@dims) reposted

Benjamin Elder
@bentheelder.bsky.social

kind v0.30.0 is out with the brand new @kubernetes.io v1.34.0 release! Try out Kubernetes 1.34 with: go install sigs.k8s.io/kind@v0.30.0 && kind create cluster github.com/kubernetes-s...

github.comRelease v0.30.0 · kubernetes-sigs/kindThis is small release containing patched dependencies and Kubernetes 1.34, as well as a bugfix for Kubernetes v1.33.0+ cluster reboots. Breaking Changes The default node image is now kindest/node:v...

Davanum Srinivas (@dims) reposted

Frederic Branczyk
@brancz.com

Ok, I have a rant I have to let go of. If you generate a change to an open-source project fully with AI, didn't read, review, understand, and questioned it, then at least have the decency to say this on the PR description. You're stealing people's time by making them review it for you.

Davanum Srinivas (@dims) reposted

Shriram Krishnamurthi
@shriram.bsky.social

Shovel-sellers made a lot of money off people who didn't know anything about mining for gold, while the latter found only a few flecks in their pans at best, and went through an "enthusiasm ⭢ increasing pain ⭢ giving up" arc as their losses added up and they decided to write off their sunk costs.

Gergely Orosz@gergely.pragmaticengineer.com

Seeing more posts like this (and I don’t mean to single out Andrea!) After enthusiasm thanks to rapid progress —> a few months of increasing pain —> giving up Turns out having a tool that generates code doesn’t remove the need to know how to program to build complex software…

Davanum Srinivas (@dims) reposted

Sedat Kapanoğlu
@ssg.dev

"Running a successful open source project is just Good Will Hunting in reverse, where you start out as a respected genius and end up being a janitor who gets into fights."

Davanum Srinivas (@dims) reposted

Matt "msw" Wilson
@msw.bsky.social

OH: "And so, it begins."

daniel:// stenberg://@bagder.mastodon.social.ap.brid.gy

Cybersecurity Risk Assessment Request https://daniel.haxx.se/blog/2025/07/11/cybersecurity-risk-assessment-request/ #curl #CRA

daniel.haxx.seCybersecurity Risk Assessment RequestWith the new EU legislation Cyber Resiliency Act (CRA), there are new responsibilities and requirements put on _manufacturers_ of digital products and services in Europe. Going forward these manufacturers must be able to know and report the exact contents of their software, called a Software Bill of Material (SBOM) and they have requirements to check for vulnerabilities in those components etc. This implies that they need to have full control and knowledge about all of their Open Source components in their stack. (See the CRA Hub for a good resource on CRA for Open Source people.) As a maintainer of a software component that is widely used, I have been curious to see how this will materialize for us. Today I got a first glimpse of what I can only guess will happen more going forward. This multi-billion-dollar Fortune-500 company that I have no contract with and with which I have had no previous communication, sent me this email asking for a lot of curl information. A slightly redacted version is shown below. Now that my curiosity has been satisfied a little bit I instead await the future and long to see how many more of these that will come. And how they will respond to my replies. CRA_request_counter = 1; ## The request > Hello, > > I hope this message finds you well. > > As part of our ongoing efforts to comply with the EU Cyber Resilience Act (CRA), we are currently conducting a cybersecurity risk assessment of third-party software vendors whose products or components are integrated into our systems. > > To support this initiative, we kindly request your input on the following questions related to your software product “libcurl” with version 7.87.0. Please provide your responses directly in the table below and do reply to all added in this email, > > Additional Information: > > * Purpose: This security assessment is part of our due diligence and regulatory compliance obligations under the EU CRA. > * Confidentiality: All information shared will be treated as confidential and used solely for the purpose of this assessment. > * Contact: Should you have any questions or need further clarification, please feel free to reach out by replying directly to this email. > > > We kindly request your response by Friday, July 25, 2025, to ensure timely completion of our assessment process. Thank you for your cooperation and continued partnership in maintaining a secure and resilient digital environment. ## My reaction and response I am not their _vendor_ without having a more formal relationship established and I am certainly not going to spend a few hours of my spare time gathering a lot of information for them for free for their commercial benefit. They “kindly” want me to respond within two weeks. Their use of double quotes around “libcurl” feels odd, and they claim to be using a version that is now more than 2.5 years old. Most if not all of the information they are asking for is already publicly and openly accessible and readable. I suspect they want the information in this more formal way to make it appear more reliable or trustworthy perhaps. Or maybe it just follows their processes better. (It also reminded me of the NASA emails.) I responded like this > Hello, > > I will be happy to answer all curl and libcurl related questions and assist you with this inquiry as soon as we have a support contract setup. You can get the process started immediately by emailing support@wolfssl.com. > > Thanks, I’m looking forward to future cooperation. > > / Daniel I will let you know if they take me up on my offer . ## The screenshot This snapshot of how it looked also shows the actual nine-question form table. Email screenshot ## Why the company name is redacted I’m looking forward to eventually do business with this company, I don’t want them to feel targeted or “ridiculed”. I also suspect that there will be many more emails like this going forward. The company name is not the interesting part of this story.

Davanum Srinivas (@dims) reposted

Yuan Tang
@terrytangyuan.xyz

🧵 Technical leadership in open source isn't about control — it's about stewardship. In OSS, you don’t manage people. You manage trust.