Deploying 1С-Bitrix in Kubernetes: Complete Guide with Case Studies

1С-Bitrix was not designed for container orchestration. Sessions in files, cache on disk, uploaded files in upload/, the core in bitrix/ — all these stateful artifacts require special handling in Kubernetes. Yet the task is solvable, and production Bitrix sites run in k8s clusters under heavy load. We have deployed Bitrix in Kubernetes for 15+ projects, and our experience shows: in 2-3 weeks you can get a fault-tolerant infrastructure with automatic scaling.

Proper containerization of Bitrix allows achieving zero downtime during deployments and easily withstand peak loads. Our clients save up to 30% on infrastructure costs, and the project pays for itself within six months. In this article, we will analyze the key problems and their solutions based on real cases.

However, many teams encounter typical mistakes: incorrect session setup leads to automatic logouts during scaling, and storing cache in files nullifies the benefits of containerization. We have collected best practices that will help you avoid these pitfalls.

Why Kubernetes for Bitrix is a Challenge?

The main problem — Bitrix stores state (sessions, cache, uploaded files) locally on disk. In Kubernetes, pods are ephemeral: data is lost when a pod is recreated. Without special settings, the user will lose the session on every request, and the cache will become useless. Additionally, the Bitrix license is tied to an IP or domain — during cloud deployment you need to ensure a stable external IP. Another complexity is handling uploaded files: in the classic scheme, all upload files are in a shared folder accessible to all web servers. Integration with 1С via CommerceML requires temporary files that must be available to all pods. Bitrix24 can also be deployed in Kubernetes, but its architecture differs — separate configuration of agents and events is required. Kubernetes documentation recommends using PersistentVolume for stateful data. We have applied this approach in 15 projects.

How We Solve the Session and Cache Problem?

Sessions. Switch session storage to Redis. In .settings.php of Bitrix, we specify:

'session' => [
    'value' => [
        'mode' => 'separated',
        'handlers' => [
            'general' => [
                'type' => 'redis',
                'host' => 'redis-service',
                'port' => 6379,
            ],
        ],
    ],
],

Cache. Change CACHE_TYPE=A to Memcached:

'cache' => [
    'value' => [
        'type' => ['memcache' => 'memcache'],
        'memcache' => [
            'host' => 'memcached-service',
            'port' => 11211,
        ],
    ],
],

Files. The upload/ directory is mounted via a PersistentVolumeClaim with ReadWriteMany mode (NFS, CephFS). The code is baked into the Docker image — this speeds up deployment and simplifies version management.

How to Configure Upload File Storage?

For storing upload files, we use a PersistentVolumeClaim with ReadWriteMany access mode. We recommend an NFS server in the cluster or a cloud file storage (e.g., Yandex Object Storage via FUSE). Important: the site code should be baked into the Docker image, and the upload directory excluded from the image via .dockerignore. This ensures files are not lost when pods are recreated. In practice, for a catalog with 2 million products, upload takes 50 GB — PV handles it without issues.

Typical Mistakes in Containerizing Bitrix

Why Should the Database Be Placed Outside the Cluster?

Although MySQL can be run in Kubernetes via StatefulSet, we strongly recommend using managed solutions (AWS RDS, Yandex Managed Service for MySQL). This simplifies backups, replication, and updates. Databases are the most critical component, and their maintenance in the cluster requires separate expertise. For example, in case of etcd failure, database recovery can take hours, while a managed solution guarantees SLA 99.95%.

Structure of Kubernetes Manifests

namespace: bitrix-prod
├── Deployment: bitrix-app (PHP-FPM + Nginx sidecar)
├── Service: bitrix-app-svc
├── Ingress: bitrix-ingress (with TLS)
├── StatefulSet: redis
├── StatefulSet: memcached
├── PersistentVolumeClaim: bitrix-upload (RWX)
├── ConfigMap: php-fpm-config
├── ConfigMap: nginx-config
└── Secret: db-credentials

Deployment for PHP-FPM with Nginx sidecar, mounting upload and configs — a standard pattern. The database (MySQL) we recommend placing in a managed solution — it is more reliable and easier to maintain.

Horizontal Scaling

After setting up Redis and Memcached, scaling is one command: kubectl scale deployment bitrix-app --replicas=5. You can add a HorizontalPodAutoscaler:

apiVersion: autoscaling/v2
kind: HorizontalPodAutoscaler
metadata:
  name: bitrix-hpa
spec:
  scaleTargetRef:
    apiVersion: apps/v1
    kind: Deployment
    name: bitrix-app
  minReplicas: 2
  maxReplicas: 10
  metrics:
    - type: Resource
      resource:
        name: cpu
        target:
          type: Utilization
          averageUtilization: 70

CI/CD Pipeline

We use GitLab CI/CD: Docker image build, push to registry, rolling update via kubectl. Zero downtime — pods are replaced one by one.

Timeline

Total: 2-3 weeks for a production environment. For dev/staging — faster.

What Is Included in the Work

• Audit of current Bitrix configuration and infrastructure.
• Development of Dockerfile and Docker Compose for local development.
• Writing Kubernetes manifests (Deployment, Service, Ingress, PVC, Secret).
• Configuration of Redis and Memcached for sessions and cache.
• Integration of CI/CD (GitLab/GitHub Actions) with rolling update.
• Load testing and optimization (up to 1000 RPS).
• Deployment and operation documentation.
• Training for your team (1-2 sessions).

Our Experience

We have been doing Bitrix infrastructure for over 7 years. We have deployed 15+ projects in Kubernetes, including catalogs with millions of products and high traffic. We use only stable technologies and best practices. One client — an online store with 2 million products and 50,000 unique visitors per day. After migration, downtime dropped to zero, and page load speed increased by 40%.

Order an audit of your infrastructure — we will assess readiness for containerization and propose an optimal plan. Contact us for a consultation.

1C-Bitrix Module Development and Setup

The main trap of Bitrix is init.php. You add an OnBeforeIBlockElementUpdate handler there, then another one — a year later the file is 2000 lines, and on every hit all that code executes. We move business logic into full-fledged modules with D7 ORM, custom tables, and administrative interface. The module can be disabled, transferred to another project, covered with tests — none of that is possible with init.php. Our team has 10+ years of Bitrix experience, certified specialists, and a 6-month code guarantee. Request a consultation — we'll explain how to migrate legacy code to a modular architecture.

Why is init.php the worst place for business logic?

Init.php does not support class autoloading, lacks an isolated namespace, cannot be unit tested, and cannot be disabled without editing the file itself. Every handler written there runs on every request, even if not needed. In a module, you register handlers through EventManager, and they only execute when the event occurs. Performance difference: up to 3x with 10+ handlers.

Standard Modules: Typical Problems and Solutions

Information blocks. IBlock architecture is the first thing we review on any project. A classic mistake: one catalog infoblock with 80 properties, 30 of which are multiple. The b_iblock_element_property table swells to millions of rows, and CIBlockElement::GetList with filtering on three properties does a full scan. We move reference data to Highload-blocks, eliminate multiple properties where possible, and design the structure for 5x growth.

e-Store (sale). Cart business rules are a separate story. We set discount priorities to prevent two campaigns from giving 60% instead of 30%, connect payment handlers, and write custom validation via OnSaleOrderBeforeSaved.

Search. The built-in search module with morphology works up to 10–15 thousand elements. Beyond that — Elasticsearch. We configure it via the Bitrix search module API, indexing through CSearchFullText or custom indexers.

Highload-blocks for dictionaries, logs, user data — instead of bloated IBlocks. Direct queries via Bitrix\Highloadblock\HighloadBlockTable, custom tables instead of the EAV structure of standard infoblocks. A million records — no degradation.

Mail events. Configuration is not just templates in b_event_message. The key is SPF, DKIM, DMARC on the DNS, otherwise transactional emails go to spam. We check deliverability and set up bounce handling.

How to Design Infoblocks for Performance?

We use Highload-blocks for reference data (colors, sizes, manufacturers) that are not involved in complex queries. For SKUs — a separate infoblock with linking via IBLOCK_ELEMENT_PROPERTY. Enable INDEX_PROPERTY for frequently filtered properties. Tagged caching: when an element changes, only the related cache is cleared. Highload-blocks process up to 10x faster than infoblocks with multiple properties on volumes of 100,000 records.

Custom Module Development

Each module follows the structure /local/modules/vendor.modulename/:

• install/index.php — setup class, create tables via $DB->RunSQLBatch()
• lib/ — D7 ORM classes, extending Bitrix\Main\ORM\Data\DataManager
• admin/ — administrative pages using CAdminList, CAdminForm
• include.php — autoloading, event handler registration via EventManager::getInstance()->registerEventHandler()
• REST API endpoints via \Bitrix\Rest\RestManager

The module registers in the system, appears in the "Installed Solutions" list, and has its own settings at /bitrix/admin/settings.php?mid=vendor.modulename. It can be enabled, disabled, and updated through UpdateSystem or custom migration mechanics.

Examples of implemented tasks:

• Campaign management — visual condition builder via CAdminCalendar, timers via agents (CAgent::AddAgent), analytics linked to the sale module
• Cost calculator — React widget on the frontend, REST API in the module, formulas stored in a Highload-block
• Booking system — real-time calendar, locking via $DB->StartTransaction() / $DB->Commit() on concurrent requests, integration with channel manager via webhook

Components and Composite Cache

Component customization via result_modifier.php and component_epilog.php, not by editing template.php of the standard template. This way core updates are painless.

Composite cache ("Composite Site" technology) — the server sends ready HTML, bypassing PHP routing. Dynamic areas (cart, authorization) are loaded via CBitrixComponent::setFrameMode(true) and AJAX. TTFB drops to 30–50 ms. But there are caveats: not all components are compatible, $APPLICATION->ShowPanel() breaks composite, and careful markup of <div id="bx-composite-..."> is required.

What to Check Before Installing a Marketplace Module?

Before installing a module from the marketplace, an audit is mandatory. We check: SQL queries without prepared statements (hello SQL injection), direct use of $_REQUEST without filtering, use of outdated kernel API instead of D7, conflicts with the composite cache module. A module with no updates for over a year and a few dozen installations is likely a problem on the next PHP update. A typical case: a module calls CIBlockElement::GetList with no cache reset — the site crashes with 5000 elements.

Migration to D7

When upgrading PHP or switching to a new edition — refactor outdated calls:

• CIBlockElement::GetList() → Bitrix\Iblock\Elements\ElementTable::getList()
• CSaleOrder::GetList() → Bitrix\Sale\Order::getList()
• CModule::IncludeModule() → Bitrix\Main\Loader::includeModule() Testing on staging, rollback via git on issues.

According to official 1C-Bitrix documentation, D7 ORM is the recommended tool for working with data, providing type safety and automatic query generation.

Comparison: Init.php vs Module

Module Development Scope and Cost

What is included in module development?

• Technical specification and architectural plan
• Code following PSR-4 and Bitrix code style
• Unit tests (PHPUnit) for business logic
• Integration tests for events and REST API
• Installation, configuration, and API documentation
• Repository and documentation access
• Administrator training for module usage
• 6-month warranty support

Estimated timelines and complexity:

Cost is calculated individually — contact us for a project estimate.

Module Testing

Unit tests via PHPUnit cover business logic: discount calculation, validation, document generation. Mocks for Bitrix\Main\Application::getConnection() allow tests to be DB-independent. Integration tests verify event handlers on a real database — OnAfterIBlockElementAdd, OnSaleOrderSaved, etc. REST API endpoints are tested via curl or PHPUnit HTTP client. Critical for modules working with b_sale_order, b_catalog_price — where errors cost money.

Compatibility is checked on PHP 7.4, 8.0, 8.1, 8.2 and editions: Standard, Small Business, Business. We check conflicts with popular marketplace modules — they often intercept the same events. Load testing: measurements on 10K, 100K, 1M records, profiling via Xdebug for memory leaks and N+1 queries.

Practical Examples

Campaign module for an electronics chain. The built-in sale module discounts did not cover scenarios like "2+1", a gift with purchase over a certain amount, or combined conditions. We built a visual builder: marketers create rules via drag-and-drop without development tickets. Campaign calendar, auto-deactivation via agents, analytics linked to b_sale_order — conversion, average check, usage count. Time to launch a new campaign dropped from two days to half an hour.

Calculator for builders. Parameters (area, materials, number of floors) → formula → preliminary estimate → lead to CRM via CRest::call('crm.lead.add'). Regional coefficients and seasonal markups from a Highload-block, material prices from 1C exchange. The number of target leads increased by a third: clients see a breakdown before calling a manager.

Booking for a hotel chain. Real-time availability via AJAX requests to a custom table vendor_booking_slots, seasonal tariff calculation, synchronization with Booking.com via channel manager API. Room locking on concurrent booking via SELECT ... FOR UPDATE in transactions. Timezones handled via \DateTimeZone — a guest from Vladivostok and a manager from Moscow see the same picture.

We will evaluate your project within one day. Write to us — we'll tell you what is included in turnkey development. Contact us for a consultation on your project. Order a custom module development — get a ready solution with documentation and support.