Kapil Agrawal

@netops2devops.net

Kubernetes platform Security Engineer by profession. Also a recovering network engineer. Open source exuberant. Fan of open standards. Spends way too much time in homelab

I’ve spent over a decade mostly working in on-prem environment (with some public cloud) building private cloud using Openstack, Kubernetes. I’m now working on a project where I’m forced to use AWS and I am starting to resent their closed lock in ecosystem.

argghhh! Working with struct tags in #Go can be such a pain sometimes 😫 specially when frameworks decide to use their own custom tags for validation. VSCode does not autocomplete those damn struct tags! If someone has better ideas I am all ears.

Been writing #Go for a year now, I always questioned the validity of generics and wondered why they were so controversial. I have finally stumbled upon my first use case where using generics actually makes sense to maintain compile time type safety while reducing boilerplate. It finally clicked!

I spent MOST of my #kubecon talking to all the project maintainers, contributors at the project pavilion trying to learn about different CNCF projects, challenges they face etc. Here are the projects I feel most enthusiastic about for the next year 1. Cilium 2. Falco 3. Inspektor Gadget

Case study: ESnet’s success with Cilium demonstrates that IPv6-only Kubernetes deployments are not only viable, but also work exceptionally well at government scale. This has provided a blueprint for other national laboratories facing similar mandates. Read more: www.cncf.io/case-studies...

ESnet (Energy Sciences Network)

ESnet, the data circulatory system for the U.S. Department of Energy faced high operational overhead from running individual VMs for a single containerized application with no unified observability…

cncf.io

I have never been a professional C/C++ programmer by trade and maybe that's why I don't understand this but after doing some beginner level exercises with #rust I don't get all the fuss around how borrower/checker rules make it complicated. Sure, it feels lot more verbose. Even more than #go

Critical thinking, curiosity and the drive to go deeper into the stack to learn something in & out appears to be diminishing as engineers become more dependent on AI generated content. People who were once "engineers" are now becoming "operators"