Title: Kubernetes Contemplations on Net Neutrality Day

---

July 3, 2017. I woke up to the sound of a thousand Chrome tabs and the faint hum of my old Macbook as it struggled with memory allocation for yet another build. Today is also supposed to be Net Neutrality Day of Action, but that’s only one small part of the day.

I spent most of yesterday wrestling with Kubernetes again, trying to get our application stack running smoothly across multiple nodes in a cluster. Helm wasn’t making things any easier—still feeling like there are too many moving parts and not enough straightforward documentation. I found myself wondering if we were jumping into this too deep for our current needs, but the promise of easier deployment and scaling was hard to ignore.

Meanwhile, I had just read about Apache Foundation’s decision to disallow the use of Facebook’s “BSD+Patent” license. It felt like another front in the war between open-source purists and corporations wanting to leverage community contributions without giving back. The irony is that these same companies are often pushing for more flexible licensing terms, but it just feels like they’re always playing both sides.

That led me to think about our own licensing policies at work. We use a lot of open-source tools, but the complexity of combining different licenses and ensuring compliance can be daunting. I might have to dig into that again soon; it’s one of those things that always comes back to haunt you.

On another front, my team was arguing about serverless vs. containerized microservices. Some were excited by the promise of Lambda and the ease of deploying stateless functions. But for our use case, I still felt like Kubernetes offered more flexibility in managing stateful applications and complex workflows. The debate is ongoing, but it’s nice to have some choices beyond “pure serverless” or “full monolith.”

Speaking of infrastructure, today my morning coffee wasn’t quite right. My home network was being a bit flaky due to some recent router updates, which led me down a rabbit hole trying to figure out if I could set up a local DNS server with bind9 for better control over hosts and services on the network. It’s always fun when your personal tech stack intersects with real problems at work.

And then there’s the eternal struggle of monitoring. Prometheus + Grafana have become our go-to tools, but setting them up consistently across multiple clusters is still a pain point. I spent some time last night trying to get our CI/CD pipeline to automatically deploy these monitoring tools as part of new cluster creation. It’s not glamorous work, but it’s important for the long-term health of our infrastructure.

As I sit here in my home office, the day seems to be going on forever with one tech problem after another. But amidst all this, there is a sense of progress and innovation. The tech landscape feels dynamic and full of possibility, even as we grapple with the challenges of complexity and scale.

So today, as Net Neutrality advocates take to the streets (or at least the internet), I’ll keep plugging away at my workday. Kubernetes, Helm, and all the other tools are helping us build a more flexible and scalable infrastructure, but there’s always room for improvement and debate. That’s what makes this field so exciting—there’s never a shortage of problems to solve or opinions to consider.

Until next time, happy coding.