🚀 Day 22 & 23 of #CKA prep!
Covered:
- Worker node troubleshooting
- Network plugin debugging
- Worker node configuration
- kubectl & Kubernetes API data
- JSON vs YAML
- Advanced JSONPath queries
Following @techie_piyush ’s CKA course. ☸️
Day 22 & 23 ✅
🚀 Day 19, 20 & 21 of #CKA prep!
Covered:
• Metrics Server & monitoring
• Logging & container runtime debugging
• Application failure troubleshooting
• Services & Network Policies
• Backend DB troubleshooting
• API Server, Scheduler & Controller Manager
• Control plane
I used to think building the solution was the hardest part.
After working in DevOps, infrastructure, and technical projects, I’ve realized something: The hardest part is often deciding what NOT to build.
A few things I’m learning while moving deeper into AI Product Management:
▶️ A problem is not automatically worth solving just because technology can solve it.
▶️ A feature is not successful because users can use it. It’s successful when it changes a meaningful user behavior or outcome.
▶️ AI makes it easier to build things quickly - which makes prioritization even more important.
▶️ Metrics should be discussed before building, not after launching.
▶️ Talking to users can reveal problems that dashboards never will.
I’m trying to combine my background with product thinking - and understand how great products are actually discovered, built, measured and improved.
Still learning. Still experimenting.
#ProductManagement #AI #AIPM #BuildInPublic #Community
🚀 Day 17 & 18 of #CKA prep!
Covered two important cluster admin tasks:
• Upgrading a multi-node cluster with kubeadm
• Kubernetes etcd backup & restore
Hands-on practice with the upgrade, backup and restore workflows.
Following @techie_piyush’s CKA course. ☸️
so @LVNilesh sir told me to try breaking into his network as a challenge
found exposed backend internals, user systems, config, and way more than I expected
and apparently the backend was happy to let me speak for it
🚀 Day 16 of #CKA prep!
Today I covered Kubernetes Ingress and how it routes external traffic to services inside a cluster.
The lecture was taught by @AbhiVeeramalla
Following @techie_piyush ’s CKA course. ☸️
Day 16 ✅
#CKA#Kubernetes#DevOps
Day 14 ✅
🚀 Back on the grind!
Couldn’t post my CKA progress for the last 5 days due to fever, but I’m back at it again. 💪
Day 14:
• DNS fundamentals
• Root Name Servers
• A & CNAME records
• DNS records & localhost
• CoreDNS in Kubernetes
• Kubernetes service discovery
Creators are enjoying Reeldrop, and it's growing significantly. Here are the stats after 40 days of launch:
💁♂️ 735 Users
🤌 9 paid users
💰 $1122 USD net revenue
📈 130k+ impressions on GSC in the last 28 days
> Shipped the features no other Instagram growth tool has, at an unbeatable price.
> The free tier is more generous than any VC backed startup
Revenue data from @trust_mrr below
Reached 100 stars on Codra.
Thank you to everyone who starred it, opened issues, or gave it a try. Means a lot for a side project.
Onward. https://t.co/7jPoxlZ2HD
🚀 Day 11 & 12 of #CKA prep!
Covered:
• Service Accounts
• Network Policies & Calico
• Restricting Pod access
• Multi-node cluster with kubeadm
• Control plane & worker setup
• Required ports & networking
Following @techie_piyush ’s CKA course. ☸️
Day 11 & 12 ✅
🚀 Day 10 of #CKA prep!
Today I covered Kubernetes RBAC:
- Roles & RoleBindings
- ClusterRoles & ClusterRoleBindings
- Namespace vs cluster-scoped permissions
Following @techie_piyush ’s CKA course and strengthening my Kubernetes administration skills. ☸️
Day 10 ✅
Free tool of the day on Codra. Regular expressions shouldn't look like alien syntax.
The Regex Explainer breaks down any complex pattern into plain English.
Automations running on ReelDrop have sent 31,316 DMs and posted 23,222 public comment replies. Between them they reached 20,454 different people.
Sunday, 6 September, was the busiest day so far, 6,786 automation events in one day. The last 7 days account for 16,386 events, 39 percent of every automation event the product has ever processed, which is 41,794 total. I opened this up publicly in August, so the curve is short and I don't want to read too much into a single week.
Then the other side of it.
528 people have signed up. 38 of them have built an automation. 122 have scheduled or published a post. Every one of those 31,316 DMs came out of that group of 38, people who set something up once and left it running.
The volume is real, and it came out of a handful of accounts.
The full list, pulled straight out of the production database on Sunday night:
• DMs: 31,316 sent, plus 11,770 taps on the "send me the link" buttons inside them
• Replies: 23,222 public comment replies posted, 2,614 timed follow-ups, 4,082 people wrote back
• Automations: 175 built, 63 of those in the last 7 days
• AI content: 267 carousel projects holding 912 AI generated slide images, and 1,974 AI captions
• Scheduler: 223 posts published, 24 more waiting to go out, 9 trial reels
• Accounts: 528 real signups, 91 in the last 7 days, 131 people connected an Instagram account
Internal and test accounts are out of all of that. 21 accounts, 30 workspaces, stripped before I counted. I'd rather post a smaller honest number than a bigger one I have to caveat later.
What I keep chewing on is the 38.
The free plan gives you 5 active DM automations and the full reels scheduler, with no credit card. A few people have told me that's too much to give away. Some folks are definitely making second accounts to farm it.
I've left it alone anyway, because the thing that makes someone upgrade is watching one of their own reels pull 200 comments and every single one of them get a DM back.
That reasoning only works if people actually get there. 38 out of 528 did. Which puts the problem somewhere well before the pricing page.
490 people signed up, looked at it, and never built the thing that would have shown them what it does. Free versus paid doesn't matter when someone never reaches the moment that sells it.
So the first ten minutes after signup are where I am losing them, and that part is on me.
The other half of it is that 122 people scheduled a post but only 38 built an automation. Scheduling is the easy habit, you already know what it does before you sign up. The automation is the part where you have to imagine the outcome before you have seen it once.
Since day 18 I shipped the Inspiration tab on 6 September, which shows your own top posts next to a swipe file you can save other people's work into. Before that, an MCP server so you can schedule reels from Claude, trial reels, first comment scheduling, and a media kit page.
The swipe file has 0 items in it so far. Launched on the 6th, so that's fair, but I'm putting it in the same post as the good numbers because that's the deal I made with myself when I started posting these.
Two other things I'll admit while I'm here. 228 DMs failed. 25 posts failed to publish, 16 of them reels. Both are small against the totals and both are still bugs someone experienced on their own account.
Something I want to ask, because I don't know the answer and 490 people are the evidence.
If you've signed up for a tool, understood what it did, and then never set the main thing up, what actually stopped you? Was it that the setup looked longer than you had time for, or that you were waiting until you had the right post to try it on?
I'm not fishing for feature requests. I want to know where the wall is. I've built one somewhere and I can't see it from where I'm standing.