Release v0.30.0

This release focuses on the ease of use with improved documentation and simplified values.yaml and introduces Azure Blob Storage as data persistence backend for pluginDaemon.

What's Changed

• Introduce Azure Blob Storage support in pluginDaemon (#279, #282, #286)
• Remove redundant resources configuration in values.yaml(#287) @Miaoxiang-philips
• Add schema validation for values.yaml (#278)
• Improve documentation and fix version inconsistency (#280, #288)
• Allow custom volume mount for sandbox (#284, #285)
• Docs: Add migration guide for built-in Redis and PostgreSQL (#289, #292)
• Remove advanced configurations for built-in Redis in favor of externalPostgres and externalRedis for production oriented scenarios (#290, #291)
• Update otel related CI values to match values.schema.json definitions (#291)
• Add explicit chart versions and image tags and fix helm installation errors in CI tests (#295, #297)
• Update python version for chart linting tests (#296)

Breaking Changes

For Users of Azure Blob Storage

If you have already applied PersistentVolumeClaim for pluginDaemon in the previous releases, pluginDaemon will no longer read from the existing PVC when Azure Blob Storage is enabled.

To maintain PVC functionality before migrating data to Azure Blob Storage:

1. Set .Values.pluginDaemon.persistence.persistentVolumeClaim.existingClaim to your existing PVC name
2. Add PLUGIN_STORAGE_TYPE=local to .Values.pluginDaemon.extraEnv (forces pluginDaemon to use the PVC instead of Azure Blob)

Once ready, migrate your data to Azure Blob Storage and remove the PLUGIN_STORAGE_TYPE=local override to use the new backend.

New Contributors

• @Miaoxiang-philips made their first contribution (#287)

Full Changelog: dify-0.29.0...dify-0.30.0