Skip to main content

Operating System Support

  • Updated

Operating System Support

Symphony is designed to run on a number of current, secure, and actively maintained operating systems. As operating systems approach their end-of-life (EOL), we will sunset support for those operating systems in your software environment.

Important: This information is being provided to assist you in planning your future upgrade projects.

Symphony 25.3 and Later

List Updated: 01 October 2025 with Symphony v25.3

Caution: Running an older, unsupported operating system in your environment is done so at your own risk. Plan and upgrade to a supported operating system for full support and functionality.

Kubernetes

Symphony is designed to be Kubernetes-native, and runs on clusters provisioned using Amazon EKS (AWS-managed Kubernetes). The underlying Linux OS is distro-agnostic as long as it supports a compatible container runtime and kubelet version.

  • Symphony Software as a Service runs on Kubernetes v1.31-v1.33, and is updated regularly.

  • For your self-hosted Symphony environment, v1.29 and above are supported.

    Important: insightsoftware strongly recommends and expects you to stay within the latest three supported EKS versions, in line with Amazon Web Services EKS version support lifecycle.

Windows

  • Windows 10, 11

  • Windows Server 2016, 2019, or 2022 (64-bit) or higher

    Note: Disable Internet Explorer Enhanced Security in Windows Server 2016 to avoid multiple Internet Explorer security notifications.

Helm Chart Updates 25.4

Update Details

Simba Intelligence Integration

  • Added Simba Intelligence as an optional subchart (OCI registry: oci://registry-1.docker.io/insightsoftware/simba-intelligence-chart).

  • Controlled via global.logi.symphony.simba.intelligence.enabled (default: false).

  • Includes dedicated database initialization (simbaintelligence), proxy routing for website (/intelligence/), MCP endpoints (/mcp, /.well-known), and ingress.yaml template for direct routing scenarios.

  • Adds validation preventing concurrent use with virtualPath feature.

PostgreSQL Migration Detection

  • Added automatic detection of existing Bitnami PostgreSQL resources during install/upgrade.

  • When global.postgresql.enabled=true and Bitnami resources are detected, the installation will fail with migration instructions unless global.postgresql.continueToUseBitnamiPostgresHelmChart=true is set.

  • This prepares users for the upcoming migration away from Bitnami PostgreSQL subchart. Introduces continueToUseBitnamiPostgresHelmChart value to explicitly control Bitnami subchart usage.

Custom RabbitMQ Implementation

 

  • Migrated from Bitnami RabbitMQ subchart to custom RabbitMQ StatefulSet implementation.

    Caution: Breaking Change: Service names changed from {{ .Release.Name }}-rabbitmq to {{ .Release.Name }}-logi-symphony-rabbitmq, secret names updated accordingly, virtual host now uses {{ .Release.Name }}-symphony, and one orphaned PVC from Bitnami RabbitMQ will remain after upgrade. Topology is automatically reconfigured.

  • Provides better control, consistency, and eliminates dependency on Bitnami subchart.

Redis Cache Provider

A new Redis cache provider implementation provider is available in the Helm chart for Kubernetes deployments, replacing the previous Bitnami dependency.

Default Module Configuration

  • Added global.logi.symphony.defaultModule parameter to set the default module for Logi Symphony.

  • Options are Managed or Discovery. When set, this value overrides the managed application configuration using the Config Override feature.

  • By default, it is empty and the managed application defaults to Discovery.

Logi AI

global.logi.symphony.ai.enabled is now deprecated.

Related articles

Comments

0 comments

Please sign in to leave a comment.

Powered by Zendesk