WOSS
Agentic CNAI: Orchestrating Cloud-Native AI Agents at Scale
Part 6 - why AI agents belong on Kubernetes, and the agentic CNAI stack that keeps them scalable, observable, and cheap
7 min read
Welzin Open Source Society
Open source built us. We're giving back.
WOSS is Welzin's open source society: plain-English learning, guided first contributions, meetups and talks, and a 30-day residency at our Mohali office where you build beside the team that runs open source in production.
- field notes published
- 10
- field notes published
- event and counting
- 1
- event and counting
- home of the 30-day residency
- Mohali
- home of the 30-day residency
What we run in production
The day job behind the society
The engineers who mentor you run DevOps, MLOps, and AIOps for clients, in production. This is that work.
DevOps
Shipping on a schedule someone answers for
CI/CD pipelines, Kubernetes platforms, and infrastructure as code - designed, built, and operated for clients who measure us on uptime, not tickets.
Kubernetes · Infrastructure as code · CI/CD · GitOps
See the servicesMLOps
Models that survive contact with production
Training-to-serving pipelines, model registries, and drift monitoring - the machinery that keeps a model earning its keep long after the demo.
Pipelines · Registries · Serving · Drift monitoring
See the servicesAIOps
Production that heals faster than it breaks
Observability, intelligent alerting, and automated remediation - so the pager stays quiet and the postmortem gets shorter every quarter.
Observability · Alerting · Auto-remediation
See the services
99.95%
uptime across platforms we operate
94%
of clients come back for the next build
6 wks
median time to first measured result
The 30-day residency · Welzin office, Mohali
Thirty days. Real contributions. Our desks.
Come work from the Welzin office in Mohali for thirty days. You contribute to real open source projects, collaborate with the engineers who run them in production, and work toward merged contributions under your name.
- Contribute
- Real issues on real projects - your pull requests, reviewed in the open, merged upstream.
- Collaborate
- Pair with the team on the same DevOps, MLOps, and AIOps work we run for clients.
- Belong
- Standups, whiteboards, chai runs - a month inside a working engineering culture.
- Free and selective - we review every application.
- Rolling admissions - apply anytime; we schedule you when a seat opens.
- Bring a laptop and curiosity; we provide the desk, the mentors, and the work.
Some residents go home with a merged PR. Some don't leave at all.
Apply for a seat
Prefer to write directly? contact@welzin.ai
The landscape
The map we work from
The foundations WOSS organizes under - Linux Foundation, CNCF, Apache - and the projects we ship code to.
Read the stack top-down, open it as a map, search it, or filter by how deeply we engage.
WOSS's pillars map to the real governance hierarchy, read top-down: the language agents speak, the engine room serving the models, the playbook AI runs by, the retrieval underneath RAG, the guardrails around every repo, the storage floor beside them, and the ground it all runs on - resting on the bedrock that hosts everything. The ASF rail feeds data in from the side. kagent is the keystone: it runs on CNCF, embodies CNAI, and speaks AAIF's MCP.
The language
AAIF
how agents behave and talk
The playbook
CNAI
how AI runs on cloud native (patterns · whitepapers)
The engine room
PyTorch Foundation
the models it serves
The retrieval
OpenSearch Foundation
the context it retrieves
The guardrails
OpenSSF
the supply-chain practices wrapping every WOSS repo
The storage floor
SODA Foundation
data & storage management - and agent context (Contexture)
The ground
CNCF
the infrastructure it runs on (Kubernetes · Prometheus · OpenTelemetry · kagent)
The bedrock
Linux Foundation
the neutral home that hosts them all (LFX · certs · events)
Second root
ASF · the data layer
The Apache pipeline that feeds every layer above: streaming ingestion, orchestrated DAGs, distributed feature engineering - the stage before training and inference.
Each Apache project is governed by its own PMC under 'the Apache Way'. Our on-ramp guidance: go deep on ONE project - docs, connectors, or a well-scoped bug.
Events & talks
Where you'll find us in the room
Past
We hosted
CNCG Chandigarh Cloud Native Meetup
CogNerd, Mohali
Amit Kumar, Nikhil Kumar, Rajan Sharma, Hrittik Roy, Yuvraj Verma, Sourabh Mittal, Nitish Kumar, Ravindra Verma, Saurabh Mishra, Saiyam Pathak
Field notes
What we're writing
Plain-English writing on Linux, cloud native, and the open source way, from the engineers who run it in production.
WOSS
AI-Ready Kubernetes: What CNCF's AI Conformance Program Actually Means
Part 7 - the new standard that turns 'AI-ready' from a marketing sticker into a test your cluster has to pass
6 min read
WOSS
Cloud Native AI in Production: Patterns, Pitfalls & a Reference Architecture
Part 5 - the practitioner's guide to running CNAI at scale, from a layered reference architecture to the anti-patterns that quietly kill teams
8 min read
Write for WOSS
Your first contribution doesn't have to be code
Field notes are written by the community as much as by us. Pitch us a draft - a guide, an explainer, a war story from production - and we'll edit it with you and publish it under your name.
Prefer email? contact@welzin.ai
Already live in git? Skip the form - open a PR.
Questions
Asked straight, answered straight
I've never used Linux or git. Is this for me?
Yes - that is exactly who the learn track is for. Step one of the pathway assumes nothing beyond curiosity and a laptop. If you can install an app, you can install a VM, and we take it from there in plain English.
How much time does it take?
A couple of hours a week moves you forward. The pathway is self-paced: some people go install-to-first-PR in a month, others take a season. There are no deadlines and nothing expires.
Is it free?
Yes, entirely. WOSS is how Welzin's engineers give back to the ecosystem their day job stands on. There is no paid tier and nothing to upsell.
Do I need to be in India or in a specific timezone?
No. Everything starts online and asynchronous - the writing, the issues, the reviews. Live sessions and in-person meetups will come as the community grows, and they will always have an async trail.
What does a founding member actually do?
You are early, so you shape it: which sessions we run first, which repos we open, what the meetups look like. Founding members get the field notes and first invites to everything, and their feedback sets the roadmap.
Why does a company run a community?
Because open source built the company. Everything Welzin ships stands on Linux, Kubernetes, and Postgres, and the engineers here grew up contributing. The day job funds the society; the society stays free.
Is the 30-day residency paid? Does it cost anything?
It costs nothing and pays nothing - it is a free, selective residency. You give a month of real contribution; we give the desks, the mentors, and the work. What you leave with is merged PRs and the people who reviewed them.
Where do I stay during the residency?
The residency runs from the Welzin office in Mohali. Travel and stay are yours to arrange - the practical logistics are covered in the reply to your application.
Can I do the residency remotely?
No - the residency is the in-person track, and being in the room is the point. Everything else on this page is the remote path: the field notes, the events, the society itself.
Join the society
Not ready for thirty days? Start with your inbox.
We’re at day zero. Founding members get the field notes first, first invites to events, and a real say in what this society becomes.
Prefer to write directly? contact@welzin.ai
Discord: opening soon
GitHub org: opening soon
Every question is welcome here. Everyone in WOSS remembers their own first pull request. We follow the Contributor Covenant.