Posts

👛 Missed the earlier phases? Start from the beginning. 🚀 The Goal In the “Run” phase, we stream real-time telemetry from an Arista cEOS container running in Kubernetes. We’ll: Enable gNMI on cEOS Install and configure gnmic Query live interface stats Deploy the topology via Clabverter to Kubernetes Set up image delivery via DigitalOcean Container Registry Optionally configure certificate-based authentication 🐳 Step 1: Push Image to DigitalOcean Container Registry (DOCR) If you’re using a private image (like Arista cEOS), upload it to DOCR:

🐣 If you missed the Crawl phase, start here. 🧭 What We’re Doing in the Walk Phase In this post, I’m using clabverter to deploy a Containerlab topology directly inside Kubernetes — specifically using Arista cEOS. We’ll walk through converting the topology, deploying it, and validating that everything’s working — ending with a live, CLI-accessible network device. ⚙️ Step 1: Define the Containerlab Topology Here’s the ceos.lab.yaml file I used:

As a Solutions Architect working with complex network automation platforms, I’ve always loved pushing the edge of what’s possible. But this series isn’t about enterprise polish or vendor demos — it’s about getting my hands dirty, testing real-world concepts, and sharing every step (and misstep) along the way. In this first post, we’ll start at the “Crawl” stage: launching a managed Kubernetes cluster on DigitalOcean as the foundation for our lab.

Hello to all readers, and welcome to my blog! My name is Cristian Cordero, and I’m thrilled to kick off this space where I’ll be sharing my experiences, insights, and journey in the fascinating world of network automation technology sales. A bit about me: Outside of the tech realm, I’m an ardent fitness enthusiast. Hitting the gym has become an almost daily ritual for me. Beyond the physical benefits, it offers me a sanctuary, a place where I can clear my thoughts, focus on my goals, and prepare myself mentally for the challenges ahead.