Nexeed
    • Introduction
    • Concepts
      • Domain model
    • User manual
      • Device types
        • Manage or create a new Measuring Point for a device type
        • Manage or create a new error definition for a device type
        • Manage devices for a device type
      • Devices
        • Manage or create a new Measuring Point for a device
        • Manage or create a new error definition for a device
      • Topology
        • Navigate the topology
      • Error definitions
      • Measuring points
      • Processes
      • Process groups
      • Material definitions
    • Operations manual
      • Overview
      • System architecture and interfaces
      • System requirements
        • Equipment management service
        • Material service
        • Messaging service
        • Nginx gateway
        • Process service
      • Migration from previous versions
        • History of current versions
        • History of older versions
      • Setup and configuration
        • Helm configuration
        • Horizontal scalability for services in HELM deployments
        • Module health verification Endpoints and K8s probes
        • Data migration & synchronization
        • mmpd/equipment-service
        • mmpd/messaging-service
        • mmpd/process-service
        • mmpd/material-service
      • Start and shutdown
      • Regular operations
        • Deletion policy
        • Entities & fields
        • Resources and roles
      • Failure handling
        • Health verification Endpoints
        • Resiliency against failures in RabbitMQ
      • Backup and Restore
      • Logging and monitoring
      • Known limitations
    • API documentations
      • Equipment HTTP API
      • Process HTTP API
      • Material HTTP API
    • Glossary
Master Data Management
  • Industrial Application System
  • Core Services
    • Block Management
    • Deviation Processor
    • ID Builder
    • Multitenant Access Control
    • Notification Service
    • Ticket Management
    • Web Portal
  • Shopfloor Management
    • Andon Live
    • Global Production Overview
    • KPI Reporting
    • Operational Routines
    • Shift Book
    • Shopfloor Management Administration
  • Product & Quality
    • Product Setup Management
    • Part Traceability
    • Process Quality
    • Setup Specs
  • Execution
    • Line Control
    • Material Management
    • Order Management
    • Packaging Control
    • Rework Control
  • Intralogistics
    • AGV Control Center
    • Stock Management
    • Transport Management
  • Machine & Equipment
    • Condition Monitoring
    • Device Portal
    • Maintenance Management
    • Tool Management
  • Enterprise & Shopfloor Integration
    • Archiving Bridge
    • Data Publisher
    • Direct Data Link
    • Engineering UI
    • ERP Connectivity
    • Gateway
    • Information Router
    • Master Data Management
    • Orchestrator

Nexeed Learning Portal

  • Master Data Management
  • Operations manual
  • Setup and configuration
  • Horizontal scalability for services in HELM deployments
preview v9.0.0

Horizontal scalability for services in HELM deployments

When using a HELM chart to deploy MDM services, you can scale the number of instances horizontally by increasing the number of replicas in the deployment. This can be done by setting the replicaCount value in the custom-values.yaml file of the umbrella chart.

The replicaCount value for Equipment, Material and Process services is set to 2 by default. This means that by default, 2 instances of every service will be deployed. For Messaging Service replicaCount value is set to 1 instance by default and should not be changed.

For example, to down scale the number of MDM Equipment Service instances to 1, set the replicaCount value to 1 in the custom-values.yaml file:

mmpd:
  deployments:
    equipment-management-service:
      replicaCount: 1

After updating the custom-values.yaml file you need to deploy the HELM chart with the updated values. This will then create 1 instance of MDM Equipment Service.

Automatic horizontal scalability is not supported for MDM in HELM deployments. You need to manually scale the number of instances by updating the replicaCount value in the custom-values.yaml file.

Do not scale Messaging Service! Scaling could affect the order of messages on the AMQP bus and thus the data integrity among other modules that rely on MDM messages.

Contents

© Robert Bosch Manufacturing Solutions GmbH 2023-2025, all rights reserved

Changelog Corporate information Legal notice Data protection notice Third party licenses