Back to Blog
Kubernetes
AWS
Tooling
Community
New policy: Sharing new Kubernetes tools must be in the weekly thread
March 3, 2026
4 min read read
# New policy: Sharing new Kubernetes tools must be in the weekly thread
## What started the discussion
Hi all. As I'm sure many of you have noticed, we've seen a sharp rise in the number of "check out this new Kubernetes tools I just made" posts. We love how excited people are about the Kubernetes ecosystem, but it's become very hard to judge if these are spam or not. So as a middle-ground we've created a new automatic weekly thread and all such posts now must go as comments in there. "New tool" posts outside of that thread will be removed. You can check out https://www.reddit.com/r/kubernetes/comments/1rea8qu/weekly_show_off_your_new_tools_and_projects_thread/ for this weeks thread to get things started! If you have any questions please ask them below or message us moderators at any time. Thanks!
## What stood out in the comments
### Discussion point 1
This is a fair objection but I think the realistic state of the world is that social media tools like Reddit are no longer good places to get visibility. There's so many new tools, some vibe coded side projects that realistically aren't that interesting to anyone but the creator, but also lots more that are "my startup is releasing this free tool which is actually an upsell for our hosted app". It all just dissolves into an overwhelming soup. But then how do new projects get off the ground if they aren't lucky enough to have an existing audience? I wish I had an answer for that but the most I can say for right now is "probably not on r/kubernetes", it's just beyond what either the mods or users can handle at this point. Maybe if someone wants to start doing some kind of weekly or monthly curation to cut through the noise? But of course if we offered that, I'm sure we would get 15 versions written by LLM to subtly promote their own projects and now we're back at square one.
### Discussion point 2
While I appreciate the reasoning behind it, hiding it in a specific thread is all even non-AI tools lose all chances at getting visibility. Nobody (relatively speaking) will actively go and look at this weekly thread. The way r/selfhosted approached this (limiting to a single day of the week) is IMHO a much better option.
### Discussion point 3
Hey guys check out this Operator I made to automatically post to the weekly Kubernetes thread
### Discussion point 4
True but have you checked out this new Kubernetes tool?
### Discussion point 5
Good decision. Thanks, it's been ruining everything. If only we could get easily rid of the AI slop "hey team what's your opinion on nonexistent problem X" posts
## Thread snapshot
- Original subreddit: r/kubernetes
- Original author: u/coderanger
- Reddit score: 145
- Comment count: 17
- Original thread: https://www.reddit.com/r/kubernetes/comments/1rembkb/new_policy_sharing_new_kubernetes_tools_must_be/
Keep Exploring
CVE-2026-22039: How an admission controller vulnerability turned Kubernetes namespaces into a security illusion
Just saw this nasty Kyverno CVE that's a perfect example of why I'm skeptical of admission controllers with god-mode RBAC.
This Valentine with Kubernetes!
This r/kubernetes discussion unpacked this valentine with kubernetes! and the practical tradeoffs engineers surfaced around it, with the original post linking out to i.redd.it.
AWS Load Balancer Controller adds general availability support for Kubernetes Gateway API
This r/kubernetes discussion unpacked aws load balancer controller adds general availability support for kubernetes gateway api and the practical tradeoffs engineers surfaced ar...
What Actually Goes Wrong in Kubernetes Production?
Hey Kubernetes folks, I’m curious to hear about real-world production experiences with Kubernetes.