> Demos over decks
A live cluster, a runnable repo, a terminal you actually type in. Talk is cheap — show the kubectl.
// cfp / submit-a-talk
Submit
a talk.
Show the kubectl.
CNSPK runs on talks from practitioners who actually shipped the thing. If you've fixed it, broken it, hardened it, or scaled it in a Pakistani team — that's a talk. First-time speakers welcome. We mentor you through it.
$ every talk turns a room into a mehfil. Bring yours.
// what-we-look-for
Real work beats hot takes.
No vendor pitches. No 40-slide intros to "what is Kubernetes." We want the demo, the incident, the config that actually ran in production.
> Pakistani context
SBP guidelines, local fintech scale, the constraints you actually work under. Global topics welcome too — grounded ones land hardest.
> Honest postmortems
The outage, the misconfig, the CVE that shipped. What broke, what you learned, what you'd do again.
> One clear takeaway
The single thing the room can apply Monday morning. If a talk has one, it's a good talk.
// review-timeline
You'll always know where you stand.
No black holes. Here's exactly what happens after you hit submit.
≤ 24 hours
Submission acknowledged
A human confirms we received your proposal. If you don't hear back in a day, ping us — something broke.
≤ 7 days
Committee review
The CFP committee reads every proposal. We may ask a clarifying question or suggest a sharper angle.
≤ 10 days
Decision
Accepted, waitlisted, or a "not this time, here's why." Every submitter gets a real answer — no silent rejections.
// first-time-speakers
Never spoken before? Perfect.
Half of CNSPK's best talks came from someone's first time on a stage. If you've got the substance but not the slides, we pair you with a mentor who's spoken at KubeCon and the chapter before. We help you scope the talk, build the demo, and run a dry-run in front of a friendly room.
You bring the work. We bring the runway. No experience required — just something real you've done with cloud-native security.
Want a mentor first? Note it in your submission, or email hi@cloudnativesecurity.pk.
// submit
Two ways in.
Pick whichever fits how you work. Both reach the same committee.
01 / GITHUB
File the CFP issue
The formal lane. Open the CFP issue template on the GitHub org, fill in the title, abstract, format, and your bio. Tracked in the open.
Open the template ↗02 / EMAIL
Email the committee
Not a GitHub person? Send the title, a short abstract, the format, and a line about you. We'll take it from there.
Email a proposal// past-accepted-talks
What's landed before.
Reference accepted talks to calibrate your pitch.
archive · empty
First CFP cycle is open
Accepted talks will be listed here as a reference for future submitters. Want to be the first one on this wall? Submit above.