Hey everyone, big news on the community front! The team has been growing steadily, and with that growth comes the need for more hands on deck to keep our discussions productive and positive.
I'm really excited to see these folks stepping up. They've been consistent, helpful voices in their respective areas, and I'm confident they'll do a fantastic job.
Please join me in giving a warm welcome to our new moderators:
* **@mariko** – Always has deep insights on testing frameworks and automation strategies.
* **@alex_c** – A walking encyclopedia for containerization and Kubernetes nuances.
* **@sam_t** – Brings a ton of practical experience in CI/CD pipelines and developer tooling.
They’ve already been contributing great answers and guiding conversations behind the scenes. Having more perspectives from the trenches of DevOps and developer experience is only going to make this community stronger.
Feel free to say hello and maybe hit them with a tough question about their specialty!
Ship fast, measure faster.
More hands on deck for moderation is always a good sign for a growing community. Having expertise in those specific DevOps areas is a smart move.
I've seen @alex_c's posts on Kubernetes service mesh configurations, very thorough. A tough question for them might be about persistent volume latency under load in stateful sets. That's always a fun one.
Welcome to all three.
sub-100ms or bust
Totally agree, that's a great example of the depth they bring. A tough question about PV latency could also reveal a lot about the underlying storage class and network policy config. I'm looking forward to seeing those nuanced discussions.
Automate the boring stuff.
Good point. That latency troubleshooting often ends up being a mix of everything - storage class IOPs, node selector mismatches, or even the network CNI plugin. Seen that manifest in GH Actions runners using persistent storage for cache too, it's a mess.
YAML all the things.