I'm doing something outside my comfort zone: I'm organizing a workshop where I'm not the one delivering the content. Here's the story. Our college cluster is great for the same reason it's unstable: anyone who asks gets sudo access. That freedom has caused real problems, like two separate Kubernetes installations running on the same machine and people killing other projects to free up a port. I think LLMs are a big part of it. Students follow whatever commands they're given without reading the explanation. So we're planning to add restrictions. We want a log of who did what, so we can call out the person when something breaks, and we want to connect all the clusters across India behind one shared URL. Honestly, I haven't done the research or planning this needs. The plan is still clay. The cluster already runs Kubernetes, and a central control plane already connects the clusters, but everyone still has raw access. To fix that properly, I needed to understand Kubernetes deeply. I did what I always do and went to YouTube. The videos were good, but none of them gave me the confidence to say "I know Kubernetes." Then the semester started, and we got a new faculty member for the DevOps class. On Krushn Sir's suggestion, I went to meet him, introduced myself, and asked if he could teach me Kubernetes. He was already teaching two students on Saturdays and invited me to join. The class was already midway, which made it hard to follow, but my YouTube background helped. He assumed I hadn't understood anything and offered to start a new class in parallel. That first class earned my huge respect. I don't remember the exact question, but I remember how he answered it. Instead of giving a memorized answer, he showed us the internals and how it actually works. The next weekend I asked when he'd start teaching me. His answer: "Find 50 students who want to learn it." That was not my kind of work. I've always handed off anything that wasn't tech, writing code, or building projects. But most of my batchmates are busy with internships, and I wasn't familiar with the juniors. So I spent the next week finding 50 serious students. I stopped people walking by, asked if they wanted to learn Kubernetes, took their phone numbers, added them to a list, and finally created one common channel for everyone. Then came the management lessons: Class announcements have to go out at least 24 hours ahead so everyone is prepared. I had to check that the room was free and the faculty was available. Whenever the faculty needed something, the answer was "talk to Kanishk," so I had to start delegating. I first gave the announcements to a junior. He had trouble getting Slack notifications, so we switched to WhatsApp. He still didn't manage it, and I ended up doing it myself. The next class turned out to be controversial. It fell on Ganesh Visarjan, which was optional, but many students wanted to shift the class. I didn't want to make shifting classes a habit, so I held it that day. Attendance dropped, but we wanted serious students anyway. The day after, I organized a revision class for those who missed it and retaught everything from the first class. I'm still figuring out this side of things, but so far it's been a great learning experience.

Read the post on X