CloudSec Burrito 2.0
Same Tortilla. Better Layers.
Over the last year (actually 8 months), I managed to publish 23 posts on this blog. It meant a lot of long days, numerous lab rebuilds, half-finished markdown litter, and more time than I care to admit staring at Kubernetes YAML wondering why something that definitely should have worked… didn’t.
Then things slowed down. December showed up. Life outside of Kubernetes continued to exist. The blog stalled a bit. Ideas did not dry up, but the process didn’t scale. Every post felt like a full production, which made consistency harder than it needed to be.
That’s what CloudSec Burrito 2.0 is about. Not writing more. Writing more intentionally.
Part of that reset is tooling and structure. I’ve moved planning and drafting from .md files scattered everywhere into Notion, as a way to enforce consistency:
Reusable post templates
Clear sections and framing
A bias toward diagrams and concrete artifacts
Less reinvention, more iteration
Same topics. Same hands-on approach. Better assembly.
What Changes in Burrito 2.0
Burrito 2.0 is about repeatable structure, not one-off essays.
Each post aims to ship at least one concrete artifact:
A diagram that anchors the idea
A runnable or inspectable example
A decision or evaluation framework
A mental model you can reuse later
And just as important:
Not every post needs to be a full sit-down meal.
You’ll see more short-form posts alongside deeper dives:
One diagram with commentary
One focused lab note or gotcha
One clarification that saves you rereading a 2,000-word post
Think fewer overstuffed burritos, more intentionally built tacos in between.
A Concrete Example: “How Do You Actually Access a Kubernetes Cluster?”
Let’s pick on one post on K8s RBAC that I like. Which makes it a good candidate to highlight improvement.
It opens with a familiar lab reality:
You’ve got a Kubernetes cluster running locally. You SSH to a node, run kubectl, and you’re in.
From there, it walks through:
SSH access to a node
kubeconfig and client certificates
Kubernetes authentication vs authorization
RBAC, ClusterRoles, and bindings
Service accounts and default tokens
The full auth → RBAC chain
Technically: solid.
Educationally: useful.
Structurally: this is where Burrito 2.0 shows its value.
How This Post Could Have Been Better (Burrito 2.0 Lens)
1. It Needed an Early Diagram
The post explains the access chain well, but only after a lot of text.
A simple diagram near the top would anchor everything that follows and give readers a mental model before diving into mechanics.
2. The “Who Am I?” Question Came Too Late
A strong idea in the article is this contrast:
Linux knows who I am.
Kubernetes often does not know the human behind the request.
That question is the hook. In Burrito 2.0, it belongs up front, not halfway down the page.
3. It Mixed “Learning” and “Operating” Without Calling It Out
The post teaches:
How Kubernetes access works
Why the default approach is risky in practice
Both are valuable, but the transition between them wasn’t explicit.
What Burrito 2.0 Optimizes For
Using that post as a reference point, Burrito 2.0 emphasizes:
Diagrams early to anchor complex flows
Clear framing questions at the start
Explicit transitions from how it works to why it matters
Shorter, focused follow-ups instead of one massive brain dump
Better layering.
Embedded Diagram Example (Mermaid)
One of the concrete changes in Burrito 2.0 is pushing diagrams earlier in the post to anchor the discussion. Instead of discovering the flow halfway through a wall of text, the idea is to make the access path explicit up front.
This diagram shows the full chain from a human on a laptop to effective permissions inside the cluster. Using my new favorite language, Mermaid!
And the payoff.
Wrap Up
CloudSec Burrito 2.0 isn’t about a new direction. It’s about a better process.
Same tortilla. Better layers. More Chipotle level wrapping.
And yes, this might be a cheat post, but it counts in my book.
