DevOps Daily with Fexingo: CI/CD, Kubernetes, and Modern Software Operations

PODCAST · business

DevOps Daily with Fexingo: CI/CD, Kubernetes, and Modern Software Operations

Lucas and Luna sit down every day to dissect the technical and operational decisions that keep modern software running. From Kubernetes cluster design and CI/CD pipeline optimizations to incident response postmortems and infrastructure-as-code strategy, this show treats DevOps as a discipline of trade-offs—not a collection of tools. Each episode starts with a specific operational scenario (a failed deployment, a costly scaling event, a security patch gone wrong) and walks through the engineering choices, metrics, and organizational patterns that led to success or failure. Lucas brings the systems-design perspective, often citing real incident reports from companies like Honeycomb, Netflix, or GitHub; Luna pushes on the human and process side—how teams communicate under pressure, how on-call rotations affect reliability, and why certain automation decisions create long-term technical debt. The listener is someone who manages or works on infrastructure teams, writes deployment configs, o

No episodes available yet.

Type above to search every episode's transcript for a word or phrase. Matches are scoped to this podcast.

Searching…

We're indexing this podcast's transcripts for the first time — this can take a minute or two. We'll show results as soon as they're ready.

No matches for "" in this podcast's transcripts.

Showing of matches

No topics indexed yet for this podcast.

Loading reviews...

ABOUT THIS SHOW

Lucas and Luna sit down every day to dissect the technical and operational decisions that keep modern software running. From Kubernetes cluster design and CI/CD pipeline optimizations to incident response postmortems and infrastructure-as-code strategy, this show treats DevOps as a discipline of trade-offs—not a collection of tools. Each episode starts with a specific operational scenario (a failed deployment, a costly scaling event, a security patch gone wrong) and walks through the engineering choices, metrics, and organizational patterns that led to success or failure. Lucas brings the systems-design perspective, often citing real incident reports from companies like Honeycomb, Netflix, or GitHub; Luna pushes on the human and process side—how teams communicate under pressure, how on-call rotations affect reliability, and why certain automation decisions create long-term technical debt. The listener is someone who manages or works on infrastructure teams, writes deployment configs, o

HOSTED BY

Fexingo

CATEGORIES

URL copied to clipboard!