Proxmox Setup

1. System Requirements Before starting, ensure your hardware meets the requirements for Proxmox. This documentation outlines the minimum and recommended specifications for CPU, memory, storage, and network. See https://pve.proxmox.com/wiki/System_Requirements 2. Prepare the Installation Media Learn how to create a bootable USB or DVD for Proxmox installation at https://pve.proxmox.com/wiki/Prepare_Installation_Media . This guide covers the tools and steps needed for preparing your installation media. 3. Installation Follow the step-by-step instructions for installing Proxmox. This includes partitioning your drives, configuring the network, and completing the initial setup. ...

August 14, 2025 · 1 min · 152 words · Dmitry Konovalov

Talos Kubernetes Initial Configuration

Client machine Talos nodes have no shell at all, so you would need some box to run configuration commands. In this case I’m using Ubuntu 22.04 LTS for console to run commands, configuring Talos 1.91 # install TalosCTL, KubeCTL, Helm curl -sL https://talos.dev/install | sh snap install kubectl --classic snap install helm --classic helm repo update Note controlplane (master) node IP and save to variable as well as some other staff ...

August 14, 2025 · 3 min · 443 words · Dmitry Konovalov

Proxmox LVM Thin Pool Auto-Extend Configuration Fix

Problem Proxmox shows this warning message: WARNING: You have not turned on protection against thin pools running out of space. WARNING: Set activation/thin_pool_autoextend_threshold below 100 to trigger automatic extension of thin pools before they get full. This warning indicates that LVM thin pools are not configured to automatically extend when they approach capacity, which could lead to VMs running out of disk space unexpectedly. Solution Configure LVM to automatically extend thin pools before they become full. ...

August 11, 2025 · 2 min · 372 words · Dmitry Konovalov

Global Contact Center Expansion (APAC)

To support growth in the Asia‑Pacific region, I spearheaded the rollout of new contact‑center infrastructure in Australia and Japan. By provisioning cloud‑based points of presence and localizing telephony functions such as IVR prompts, text‑to‑speech, and call recording, the team delivered low‑latency service that met regional data‑residency rules. Infrastructure‑as‑code templates allowed us to replicate the North American architecture while making necessary regional adaptations. The expansion reduced latency for local users and enabled new channel partnerships in the APAC market. Highlights Regional Coverage: Established fully operational contact center points-of-presence in Sydney and Tokyo, extending service capabilities across the entire APAC region Latency Reduction: Achieved 85% reduction in voice and data latency for APAC users by moving from North American infrastructure to local deployments Compliance Adherence: Successfully implemented data residency controls meeting both Australian Privacy Act and Japanese APPI regulatory requirements Scalability: Designed infrastructure to handle 300% projected growth over three years without significant architectural changes Time-to-Market: Completed full deployment within 4 months, 2 weeks ahead of schedule, enabling accelerated market entry How It Works The APAC contact center infrastructure operates on a distributed cloud architecture with regional redundancy. Each regional deployment consists of: ...

3 min · 570 words · Dmitry Konovalov