Releases: neo4j/helm-charts
Releases · neo4j/helm-charts
v2025.6.2
v5.26.9
- Update to Neo4j 5.26.9 as the new baseline, see Release notes for details of changes
- Patch CVE-2025-22870
v2025.6.0
- Update to Neo4j 2025.06.0 as the new baseline
- See Release notes for details of changes
- Added SpeeDy configuration (default:false)
❗ IMPORTANT: Backup Architecture Enhancement
Neo4j Helm Charts Backup: Migration to Native Mode
What's Changing
We've upgraded the Neo4j backup functionality from wrapper mode to native mode for improved performance, reliability, and cloud provider integration.
🛠️ Migration Guide
- Azure Users: Update your credentials secret with service principal information as follows:
# Azure credentials file
AZURE_STORAGE_ACCOUNT=your_account
AZURE_STORAGE_KEY=your_key
AZURE_CLIENT_ID=your_service_principal_id
AZURE_CLIENT_SECRET=your_service_principal_secret
AZURE_TENANT_ID=your_tenant_id
- GCP Users: Consider migrating to workload identity for enhanced security
- AWS Users: No changes required for existing configurations
- All Users: Review backup job resource allocations for optimal performance
📚 Documentation Updates
Updated documentation will be available at: Neo4j Kubernetes Operations Manual
🔧 Key Improvements
- Better Performance: Direct integration with Neo4j's native backup operations
- Removed the need for local mount for backups: Backups performed directly to cloud storage
- Enhanced Cloud Authentication: Native Azure service principal support with
DefaultAzureCredential
- GCP Workload Identity: Full support for Google Cloud workload identity authentication
v2025.5.0
- Update to Neo4j 2025.05.0 as the new baseline
- See Release notes for details of changes
- Azure blob URL is now configurable
- Fixed issue where the first node would fallback to standalone even when setting
minimumClusterSize
to 3 - Fixed parsing of multiple endpoints for backup
- Fixed consistency check failing when a database name was not defined
- Fixed boolean to string conversion issue in GO
❗ IMPORTANT: Backup Architecture Enhancement in Next Release
Neo4j Helm Charts Backup: Migration to Native Mode
📅 Effective in Release: 2025.6.0
What's Changing
We're upgrading the Neo4j backup functionality from wrapper mode to native mode for improved performance, reliability, and cloud provider integration.
🛠️ Migration Guide
- Azure Users: Update your credentials secret with service principal information as follows:
# Azure credentials file
AZURE_STORAGE_ACCOUNT=your_account
AZURE_STORAGE_KEY=your_key
AZURE_CLIENT_ID=your_service_principal_id
AZURE_CLIENT_SECRET=your_service_principal_secret
AZURE_TENANT_ID=your_tenant_id
- GCP Users: Consider migrating to workload identity for enhanced security
- AWS Users: No changes required for existing configurations
- All Users: Review backup job resource allocations for optimal performance
📚 Documentation Updates
Updated documentation will be available at: Neo4j Kubernetes Operations Manual
🔧 Key Improvements
- Better Performance: Direct integration with Neo4j's native backup operations
- Removed the need for local mount for backups: Backups performed directly to cloud storage
- Enhanced Cloud Authentication: Native Azure service principal support with
DefaultAzureCredential
- GCP Workload Identity: Full support for Google Cloud workload identity authentication
v5.26.8
- Update to Neo4j 5.26.8 as the new baseline, see Release notes for details of changes
- Azure blob URL is now configurable
- Fixed issue where the first node would fallback to standalone even when setting
minimumClusterSize
to 3
v5.26.7
- Update to Neo4j 5.26.7 as the new baseline, see Release notes for details of changes
- Fixed parsing of multiple endpoints for backup
- Fixed consistency check failing when a database name was not defined
- Fixed boolean to string conversion issue in GO
v4.4.44
v4.4.43
v5.26.6
- Update to Neo4j 5.26.6 as the new baseline, see Release notes for details of changes
- Fixed issue with wrong Source Code version on 5.26 package
- Fixed issue with handling of keepBackupFiles in env variables
- Security related dependency upgrades
v2025.4.0
- Update to Neo4j 2025.04.0 as the new baseline
- See Release notes for details of changes
- Security related dependency upgrades