Nexeed
    • Introduction
    • Getting started
      • Getting access
      • Login
      • Main screen
      • Welcome dashboard
      • Detecting process anomalies
      • Analyzing data and detecting event sequences
      • Analyzing KPIs
    • How-tos
      • Monitors on production lines
        • Configuring the automatic login in the Nexeed Industrial Application System
        • Configuring the automatic login to the identity provider with the Windows user
        • Setting cookies in the browser
        • Configuring the automatic logout in the Nexeed Industrial Application System
        • Configuring the command line parameters in the browser
        • Known limitations and troubleshooting
      • Try out the APIs
    • Integration guide
      • Underlying concepts
        • Underlying concepts
        • Onboarding
        • Security
        • Communication
      • Integration journey
      • Overview of APIs
    • Operations manual
      • Release
      • System architecture and interfaces
      • System requirements
        • Cluster requirements
        • Database requirements
        • Support for service meshes
      • Migration from previous Nexeed IAS versions
      • Setup and configuration
        • Deployment process
        • Deployment with Helm
        • Advanced configuration
        • Integrations with external secret management solutions
        • Context paths
        • Service accounts and authorizations
        • Validation tests
        • Setup click once
        • Database user setup and configuration
      • Start and shutdown
      • Regular operations
        • User management & authentication
        • How to add additional tenants
        • How to access the cluster and pods
        • Automatic module role assignments in customer tenants
        • User credentials rotation - database and messaging secrets
      • Failure handling
        • Failure handling guidelines
        • Ansible operator troubleshooting
        • How to reach BCI for unresolved issues
      • Backup and restore
      • Logging and monitoring
        • The concept and conventions
        • ELK stack
        • ELK configurations aspects for beats
        • Proxy setup for ELK
        • Health endpoints configurations
      • Known limitations
      • Supporting functions
      • Security recommendations
        • Kubernetes
        • Security Best Practices for Databases
        • Certificates
        • Threat detection tools
    • Infrastructure manual
      • Release
      • System architecture and interfaces
        • RabbitMQ version support
      • System requirements
      • Migration from previous Nexeed infrastructure versions
      • Setup and configuration
        • Deployment process of the Nexeed infrastructure Helm chart
        • Deployment with Helm
      • Start and shutdown
      • Regular operations
        • RabbitMQ
          • User management & authentication
          • Disk size change
          • Upgrade performance with high performant disk type
          • Pod management policy
      • Failure handling
        • Connection failures
        • Data safety on the RabbitMQ side
        • Fix RabbitMQ cluster partitions
        • Delete unsynchronized RabbitMQ queues
        • How to reach BCI for unresolved issues
      • Backup and restore
      • Logging and monitoring
      • Known limitations
    • Glossary
    • Further information and contact
Industrial Application System
  • 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

  • Industrial Application System
  • Operations manual
  • System requirements
  • Cluster requirements
preview 2025.03.00

Cluster requirements

The Nexeed Industrial Application System is an advanced software solution designed for industrial environments. The Nexeed IAS provides a range of features and functionalities that make it a powerful tool for managing and optimizing industrial processes. In order to run this application, a Kubernetes cluster with version 1.27 or higher and Helm with version 3.10 or higher is required. This ensures that the software can take advantage if the latest features and capabilities of the Kubernetes platform, allowing it to provide optimal performance and scalability. There is a set of specific features that are required for the cluster to fully support Nexeed IAS. These include:

There is a set of specific features that are required for the cluster to fully support Nexeed IAS. These include:

  • Ingress Controller: NGINX ingress with SSL-enabled ports (ports 80 and 443) with version 1.11.2 or higher

  • Storage plugins : blockdevice and sharedfs

  • Permission to run k8s operators (possibility to define CRDs and a cluster role governing access to the created CRDs)

  • Wildcard certificates and Wildcard domain name (optional)

  • Access to the kubernetes cluster and possibility to use binaries for management (Kubectl, Helm, K9s)

  • For deployments of more than ten application modules, usage of a Postgres database to store the helm secrets (more details in HelmStorageBackends)

External dependencies

Depending on the chosen module configuration some of the following external dependencies might be needed (for details please consult Database requirements and the operation’s manual corresponding to each module):

  • Relational database (MSSQL or Oracle)

  • InfluxDB

  • Kafka

  • Redis

  • MongoDB

Nexeed infrastructure Helm chart

The Nexeed IAS Infrastructure Helm Chart is needed if the business modules require the following dependencies:

  1. RabbitMQ

The Nexeed Infrastructure Helm chart should be installed after the installation of the Kubernetes components (CRD, namespaces, ClusterRoles) and before the application components, as some of the application components are relying on the middleware applications that the Nexeed Infrastructure Helm chart provides.

The recommended version of the Nexeed Infrastructure Helm chart to be used is 1.3.x which comes with RabbitMQ 3.13.x.

Contents

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

Changelog Corporate information Legal notice Data protection notice Third party licenses