Resource requirements per pod

The following table outlines the recommended resource requests for each pod. These recommendations assume:

No CPU limits^[1] are configured.
The underlying infrastructure does not employ CPU over-provisioning.
The CPU request values are intentionally set low because they represent resources exclusively reserved for the Pod. However, since Pods may occasionally require additional CPU, it’s important to keep extra CPU capacity available to accommodate these temporary spikes and ensure smooth performance.

Failure to meet these recommendations may result in instability or performance degradation. Volume storage is not required.

CPU Request^[2] (milliCPU)	100m
Minimum memory	500 MB
Maximum memory	2048 MB
Mounted Volume Storage	None

CPU Request^[2] (milliCPU)

100m

Minimum memory

500 MB

Maximum memory

2048 MB

Mounted Volume Storage

None

Required software on cluster

Operating System	Linux with an OCI-compatible runtime (Kubernetes)
Kubernetes Version	1.26 or higher
IAS Helm Schema Version	2.3
Further Software	N/A

Operating System

Linux with an OCI-compatible runtime (Kubernetes)

Kubernetes Version

1.26 or higher

IAS Helm Schema Version

2.3

Further Software

N/A

Infrastructure services

Service	Operational Routines
IAS Portal	Required
MACMA	Required
Master Data Management (MDM)	Required
RabbitMQ	Required
Information Router	Not required
Deviation Processor	Required

Service

Operational Routines

IAS Portal

Required

MACMA

Required

Master Data Management (MDM)

Required

RabbitMQ

Required

Information Router

Not required

Deviation Processor

Required

Other required services

Service	Operational Routines
Config Bridge (SfM Essentials)	Optional
KPI Reporting (SfM Essentials)	Optional
Maintenance Management	Not required

Service

Operational Routines

Config Bridge (SfM Essentials)

Optional

KPI Reporting (SfM Essentials)

Optional

Maintenance Management

Not required

Databases

Operational routines supports Oracle and Microsoft SQL Server.

Oracle database

Supported Versions	Oracle 19c Enterprise
DBs / Schemas / Users	Configurable
Character set	(strongly recommended) AL32UTF8
National Character set	(required) AL16UTF16
Required Privileges	NEXEED_BASIC_ROLE, NEXEED_EXTENDED_ROLE, NEXEED_MONITORING_ROLE. The roles are defined in the Nexeed IAS Operations Manual, Chapter 6.10. Database User Setup and Configuration.
Relative Capacity	Depends on amount of tenants, users, applications and resources managed

Supported Versions

Oracle 19c Enterprise

DBs / Schemas / Users

Configurable

Character set

(strongly recommended) AL32UTF8

National Character set

(required) AL16UTF16

Required Privileges

NEXEED_BASIC_ROLE, NEXEED_EXTENDED_ROLE, NEXEED_MONITORING_ROLE. The roles are defined in the Nexeed IAS Operations Manual, Chapter 6.10. Database User Setup and Configuration.

Relative Capacity

Depends on amount of tenants, users, applications and resources managed

Create Oracle schema

The following script creates an empty operational routines schema. This script is not necessary within Bosch as database provisioning will be done by Bosch Digital.

Please replace the following placeholders before executing this script.

$$SchemaUsername$$
$$SchemaPassword$$
$$DATAFILEPATH_1$$

-- create tablespaces
CREATE BIGFILE TABLESPACE $$SchemaUsername$$DATA_OPERATIONAL_ROUTINES DATAFILE '$$DATAFILEPATH_1$$' SIZE 1G AUTOEXTEND ON NEXT 500M MAXSIZE 50G;

-- create users
create user $$SchemaUsername$$ identified by $$SchemaPassword$$
  default tablespace $$SchemaUsername$$DATA_OPERATIONAL_ROUTINES
  temporary tablespace TEMP
  quota unlimited on $$SchemaUsername$$DATA_OPERATIONAL_ROUTINES;

Microsoft SQL Server

Supported Versions	minimum 2016
DBs / Schemas / Users	Configurable
Required Privileges	Full access to manage objects and data within the schema DDL + DML
Relative Capacity	Depends on amount of tenants, users, applications and resources managed

Supported Versions

minimum 2016

DBs / Schemas / Users

Configurable

Required Privileges

Full access to manage objects and data within the schema DDL + DML

Relative Capacity

Depends on amount of tenants, users, applications and resources managed

Required resources

Resources	Comments
key store and trust store	keys and certificates required for mTLS, TLS certificates are mounted into docker containers

Resources

Comments

key store and trust store

keys and certificates required for mTLS,
TLS certificates are mounted into docker containers

Messaging middleware

RabbitMQ as AMQP broker

Supported Versions	Any version supporting AMQP 0.9.1
Extensions	None
Queues / Topics / Exchanges	The exchange x.nexeed.integration on the RabbitMQ instance and a corresponding MACMA instance for emitting the integration events is required for receiving the tenant deletion/creation events.
Relative Capacity	2 incoming message per tenant

Supported Versions

Any version supporting AMQP 0.9.1

Extensions

None

Queues / Topics / Exchanges

The exchange x.nexeed.integration on the RabbitMQ instance and a corresponding MACMA instance for emitting the integration events is required for receiving the tenant deletion/creation events.

Relative Capacity

2 incoming message per tenant

1. spec.resources.limits.cpu or spec.containers[].resources.limits.cpu.

2. spec.resources.requests.cpu or spec.containers[].resources.requests.cpu.