Logo Francesco Montelli
  • Home
  • About
  • Technologies
  • Experiences
  • Education
  • More
    Projects Publications Recent Posts
  • Posts
  • Notes
  • English
    Italiano English
  • Dark Theme
    Light Theme Dark Theme System Theme
Logo Inverted Logo
  • Tags
  • Architecture
  • Automation
  • CAPI
  • Cluster API
  • Containerization
  • Day 1 Operations
  • DevOps
  • Distributed Systems
  • Docker
  • Grafana
  • Homelab
  • Image Builder
  • Infrastructure as Code
  • Ingress
  • Instrumentation
  • Kind
  • Kubernetes
  • LGTM Stack
  • Linux
  • Local Development
  • Logging
  • Loki
  • Metrics
  • Mimir
  • Monitoring
  • N8n
  • NGINX
  • Observability
  • OpenTelemetry
  • Performance Testing
  • Prometheus
  • Proxmox
  • Quality
  • Self-Hosted
  • Software
  • SRE
  • Telemetry
  • Tempo
  • Testing
  • Tracing
  • Ubuntu
Hero Image
CAPI Part 1: From Chaos to Automation

The Problem of Manual Kubernetes Management Managing Kubernetes clusters represents one of the most complex challenges in the modern cloud-native ecosystem. As the number of nodes and clusters grows, operational complexity increases exponentially, quickly making operations like provisioning new workers, coordinated control plane upgrades, network configuration management, and underlying infrastructure maintenance unmanageable. Limitations of Traditional Methods Traditional methods for managing Kubernetes clusters typically rely on: Custom scripts for node provisioning and configuration Manual procedures documented, hopefully, for upgrades and maintenance Static configurations difficult to version and replicate Imperative approaches that describe “how to do” rather than “what to achieve” Concrete Operational Problems According to CNCF surveys, operational complexity represents one of the main challenges in enterprise Kubernetes adoption.

  • Kubernetes
  • CAPI
  • Cluster API
  • Infrastructure as Code
  • DevOps
  • Automation
Tuesday, August 5, 2025 | 6 minutes Read
Hero Image
CAPI Part 2: Anatomy of Cluster API - Components and Mechanisms

CAPI Component Architecture Cluster API implements a modular architecture based on the Kubernetes controller pattern, where each component has specific and well-defined responsibilities. This separation of responsibilities ensures extensibility, maintainability, and testability of the system. Management Cluster vs Workload Cluster The fundamental distinction in CAPI is the separation between the cluster that manages infrastructure and the clusters that run application workloads. Management Cluster The Management Cluster serves as the central control hub for Kubernetes infrastructure. Its main characteristics include:

  • Kubernetes
  • CAPI
  • Cluster API
  • Infrastructure as Code
  • DevOps
  • Automation
Tuesday, August 5, 2025 | 9 minutes Read
Hero Image
CAPI Part 3: Talos Linux - The Operating System for Kubernetes

The Immutable OS Paradigm for Kubernetes Traditional operating system management in Kubernetes environments presents numerous challenges: configuration drift, extended attack surface, maintenance complexity, and inconsistency between environments. Talos Linux represents a revolutionary approach that completely redefines how operating systems interact with Kubernetes. Problems with Traditional Operating Systems Configuration Drift and Snowflake Servers Traditional operating systems (Ubuntu, CentOS, RHEL) in Kubernetes environments suffer from structural problems: # Typical scenario on an Ubuntu node ssh worker-node-01 sudo apt update && sudo apt upgrade -y sudo systemctl restart kubelet # One month later... ssh worker-node-02 sudo apt update && sudo apt upgrade -y # Different versions, divergent configurations, inconsistent behaviors According to the 2023 State of DevOps Report, over 60% of organizations struggle with inconsistent configuration management in distributed systems.

  • Kubernetes
  • CAPI
  • Cluster API
  • Infrastructure as Code
  • DevOps
  • Automation
Tuesday, August 5, 2025 | 10 minutes Read
Hero Image
Self-Hosted n8n Deployment in Homelab

Context and Motivations n8n is a powerful open-source workflow automation tool that allows connecting a wide range of services through configurable nodes. Unlike SaaS (Software as a Service) alternatives like Zapier or Make, n8n can be installed in self-hosted mode, ensuring full control over data, privacy, and extensibility. The goal of this project is to illustrate how to create a fully automated n8n instance within a home lab environment. The following technologies will be used:

  • n8n
  • Automation
  • Homelab
  • DevOps
  • Self-Hosted
Sunday, July 20, 2025 | 10 minutes Read
Navigation
  • About
  • Technologies
  • Experiences
  • Education
  • Projects
  • Publications
  • Recent Posts
Contact me:
  • francesco@montelli.dev
  • monte97
  • Francesco Montelli

Liability Notice: Privacy Policy.


Toha Theme Logo Toha
Francesco Montelli
P.IVA: 02726990399
Powered by Hugo Logo