Automation on Landry Zetam - Tech Blog

From Transcripts to Summaries: Completing the Audio Pipeline

Sat, 20 Dec 2025 00:00:00 +0000

Remember that audio transcription pipeline I built? Raw recordings flow in, get compressed, transcribed by Whisper, and stored as JSON. Great for archival, but 204 transcript files sitting on NFS storage aren’t exactly useful. Today I’ll show you how I completed the loop—automatically summarizing transcripts with an LLM and publishing everything to my Obsidian vault.

Part 1: The Problem with Raw Transcripts

The original pipeline worked beautifully. Every morning, new transcripts appeared as JSON files:

Complete Kubernetes Security Pipeline - Kube-bench and Kubescape to Obsidian

Fri, 19 Dec 2025 00:00:00 +0000

What if your Kubernetes cluster could write comprehensive security reports directly into your second brain every night? Not just one perspective, but two complementary views: infrastructure security and workload security. I built exactly that—a pipeline combining kube-bench (CIS benchmarks) and kubescape (NSA/MITRE frameworks) that publishes human-readable reports to Obsidian automatically. Here’s how the complete system works.

Part 1: Why You Need Both Tools

The Security Visibility Gap

Running a Kubernetes homelab means wearing many hats. Security scanning tools exist, but most people either:

Building a Kubernetes Security Reporter for Obsidian

Wed, 17 Dec 2025 00:00:00 +0000

What if your Kubernetes cluster could automatically write security reports directly into your second brain? Today I built exactly that—a system that runs CIS benchmark scans against my K3s cluster and publishes the results as beautifully formatted Obsidian notes. No more checking dashboards or parsing JSON files; just open your vault and see your cluster’s security posture.

Part 1: The Problem

Security Visibility in a Homelab

Running a Kubernetes homelab means wearing many hats: developer, operator, and security engineer. Tools like kube-bench exist to scan your cluster against CIS benchmarks, but they typically output JSON or text that sits in a PersistentVolume gathering dust.

Building an Automated Audio Transcription Pipeline on Kubernetes

Fri, 12 Dec 2025 00:00:00 +0000

Every day, raw audio recordings land on an SFTP server. By morning, they’re compressed, transcribed, and stored as searchable JSON - all without human intervention. Here’s how I built this pipeline on my homelab Kubernetes cluster.

The Problem

I had a growing collection of audio recordings that needed transcription. Manual processing wasn’t sustainable: download files, compress them, run through a transcription service, organize the output. This needed automation.

The requirements were straightforward:

From GitHub Notes to Production Blog

Thu, 07 Aug 2025 00:00:00 +0000

Why This Guide Exists

I’ve been doing a lot of dev work, research and hadn’t really thought about sharing the knowledge without having to learn frontend development or maintain complex code. I knew I had a bunch of markdown GitHub notes and thought they could be used as a baseline to catch up on all my lack of documentation. Then I found Hugo.

This guide covers the entire workflow of creating a Hugo blog, containerizing it, and deploying it to Kubernetes - all without writing a single line of frontend code (html, css, js).

Self-Hosting n8n on Kubernetes for AI Automation

Thu, 07 Aug 2025 00:00:00 +0000

Overview

N8N is an open-source workflow automation tool deployed in the Fako cluster. It provides a visual interface for creating complex automation workflows, integrating with hundreds of services and APIs. N8N allows you to automate repetitive tasks, connect different services, and build sophisticated data pipelines without extensive coding.

Key Features

Visual Workflow Builder: Drag-and-drop interface for creating automations
200+ Integrations: Pre-built nodes for popular services
Self-Hosted: Full control over your data and workflows
PostgreSQL Backend: Reliable storage using the cluster’s PostgreSQL
Webhook Support: Trigger workflows via HTTP webhooks
Custom Functions: JavaScript code support for complex logic
Fair-Code License: Source available with sustainable business model

Architecture

Components

Deployment: Single-replica deployment (stateful workflows)
Service: ClusterIP service on port 5678
Ingress: HTTPS access at n8n.landryzetam.net
Storage: PersistentVolumeClaim for workflow data
Database: PostgreSQL for workflow definitions and execution data
External Secrets: Database credentials from AWS Secrets Manager

Resource Requirements

Memory: 512Mi (request), 2Gi (limit)
CPU: 250m (request), 1000m (limit)
Storage: Persistent volume for N8N data and files
Database: Uses shared PostgreSQL cluster

Configuration

Environment Settings

Parameter	Value	Description
`N8N_HOST`	`n8n.landryzetam.net`	External hostname
`N8N_PORT`	`5678`	Application port
`N8N_PROTOCOL`	`https`	External protocol
`WEBHOOK_URL`	`https://n8n.landryzetam.net/`	Webhook base URL
`GENERIC_TIMEZONE`	`America/New_York`	Timezone for scheduling
`N8N_METRICS`	`true`	Enable metrics endpoint
`N8N_TEMPLATES_ENABLED`	`true`	Enable workflow templates

Database Configuration

Type: PostgreSQL
Host: postgres-cluster-rw.postgres.svc.cluster.local
Database: app
User: app
Password: Managed via External Secrets

Usage

Accessing N8N

External access:

GitOps in Practice: Managing k8s with FluxCD

Wed, 06 Aug 2025 00:00:00 +0000

After running the Fako Cluster for several months, I can confidently say that adopting GitOps with FluxCD has been one of the best decisions for managing my Kubernetes infrastructure. In this post, I’ll share practical insights and patterns that have proven invaluable.

What is GitOps?

GitOps is a way of implementing Continuous Deployment for cloud native applications. FluxCD is designed to simplify that, making it easier than ever to manage your Kubernetes environments. Here’s why i leverage it in my workflow: