HabrAugust 11, 2026🇷🇺Translated from Russian

Building Secure MLOps Platforms in Air-Gapped Environments for DevOps Engineers

The article presents a practical guide for DevOps engineers tasked with building an MLOps platform inside a fully closed, air-gapped environment. Up to 80 percent of machine-learning projects reportedly never reach production because of missing reproducible processes for data, models, and deployment.

MLOps extends classic DevOps practices to data and models. Data becomes a first-class artifact that must be versioned with DVC and stored in MinIO, while experiments are tracked in MLflow backed by PostgreSQL. A Model Registry with champion and challenger aliases allows safe model rollouts without changing application code.

The platform runs on two physical segments: a Kubernetes cluster handling serving, storage, and monitoring, and a separate GPU server used exclusively for training via Docker containers with NVIDIA runtime. This separation prevents expensive GPU resources from being locked to Kubernetes nodes.

Key components include ArgoCD with Apps-of-Apps pattern, GitLab CI/CD, FastAPI inference service, Celery and Redis for GPU task queuing, JupyterLab for experiments, OpenBao instead of Vault, External Secrets Operator, Trivy and Bandit scanning, and Prometheus plus Grafana monitoring. All Helm charts are vendored inside the Git repository to eliminate external dependencies.

Security measures specific to closed contours cover private Harbor registry, SOPS encryption with age keys delivered via ArgoCD CMP sidecar, wildcard TLS certificates distributed by ClusterExternalSecret, and a Docker Socket Proxy that restricts container operations to the minimum required privileges.

The author deliberately avoids Kubeflow because of its cloud-oriented design and heavy CRDs, and replaces Airflow with the lighter Celery queue. The resulting stack provides a reproducible, auditable foundation that can later be scaled when project volume increases.

Related articles

HabrOther

How the Modern Web and HTTPS Emerged from Simple Two-Computer Networks

The article traces the evolution of internet infrastructure from two friends connecting PCs with twisted-pair cable and assigning IP addresses to the global system of DNS, routing, and public-key certificates. It explains how early local networks expanded with switches, always-on servers, and domain names to solve the problem of changing IP addresses. As networks grew and interconnected through routers and ISPs, new risks of eavesdropping and traffic redirection appeared on open paths. The solution introduced centralized certificate authorities such as the fictional Sectigo that issue chained certificates rooted in pre-installed trust stores. The piece details the structure of certificates, key pairs, signing chains, and the browser validation process that enables encrypted HTTPS sessions. Written in accessible language with deliberate simplifications, the text serves as an educational overview rather than a technical manual.

AntiMalwareOther

Russian Neighbors Fined Over 200,000 Rubles for Defamatory Remarks in Apartment Building Chat as Supreme Court Upholds Ruling

Two women who participated in a shared apartment building chat have been ordered to pay more than 200,000 rubles in total after a court found their messages about a neighbor to be defamatory. The case began when residents complained about noisy tenants and escalated into mutual insults exchanged in the group chat, via SMS, and during phone calls. The apartment owner filed a lawsuit for protection of honor and dignity after police found no administrative violation in his actions as landlord. A linguistic expert determined that several public messages, while free of direct profanity, contained derogatory characterizations and implications of mental illness that could not be considered acceptable value judgments. The court awarded more than 100,000 rubles against one defendant and a slightly smaller sum against the second, taking into account the plaintiff's own conduct during the conflict. All appeals were rejected, including by the Supreme Court, establishing that even indirect humiliating statements about an identifiable person in a building chat can result in substantial financial liability.

AntiMalwareOther

Samara University Study Shows Social Ties Maintain Order in Minecraft Virtual Cities

Researchers from Samara University examined how player-run cities in Minecraft sustain order without heavy reliance on formal rules or enforcement mechanisms. Olga Udalova conducted eight interviews with virtual mayors and surveyed 246 players across multiple communities. The study found that dense social connections, personal reputation, and informal authority of mayors play a far greater role than written regulations. In some cities detailed norms exist while others operate with minimal rules, simply requiring players to act reasonably. A notable example is Boostergrad, a semi-anarchic community of 117 residents where griefing is formally permitted yet rarely occurs because reputational damage outweighs any short-term gain. Residents resolve conflicts through negotiation and voluntarily compensate for damage, as illustrated by one player who paid 2000 units of in-game currency after accidentally destroying another’s loot. Overall the research demonstrates that trust and social networks, rather than fear of punishment, keep these virtual societies stable.

SecuritylabOther

Why Automation Alone Fails to Improve SOC Efficiency: The Case for Managed Operational Models

Mature security infrastructure does not guarantee protection against cyber threats, as attacks can still cause downtime, crisis recovery, and financial damage even when key controls are deployed. Automation of routine tasks helps speed up responses but cannot raise SOC effectiveness without clear decision criteria, defined responsibilities, and repeatable incident-handling processes. Organizations using an average of 83 security tools from 29 vendors face fragmentation that automation alone cannot resolve. A managed SecOps model covering the full incident lifecycle—from detection and prioritization through investigation, response, closure, and post-incident improvement—is required. Positive Technologies highlights that SecOps platforms such as MaxPatrol 360 provide the unified environment needed to link context, processes, coordination, automation, metrics, and continuous improvement.