Release v0.29.0

This release bumps dify version to 1.8.1 and migrates registry of built-in Redis PostgreSQL to the use the Bitnami Legacy repository to ensure continued functionality. For further info please refer to bitnami/containers#83267.

What's Changed

• Migrate default registry from bitnami to bitnamilegacy for built in Redis and PostgreSQL (#255, #256) @BorisPolonsky
• Fix missing S3 IAM configuration (#248, #249) @titowoche30 @BorisPolonsky
• Add Open Telemetry configuration (#250) @Sn0rt
• Removed invalid PostgreSQL connection pool configuration (#263) @majian159
• Fix typo in CELERY_BROKER_URL in ExternalSecretsOperator scenarios (#264)
• Remove PVC when TOS were applicable as external storage backend for api and worker (#269) @gsakun
• Fix TOS configuration in pluginDaemon (#274) @gsakun

New Contributors

@titowoche30 @majian159 @gsakun

N.B: Migration Note

For users using built-in Redis and PostgresSQL with default image settings please beware of the changes below:

• Possible downtime of Redis and PostgreSQL: These containers will restart upon upgrading to this release as images will be pulled from bitnamilegacy instead since this version. The digest of these images, however, will remain the same. Such impact was caused by the new Bitnami Secure Images initiative.
• Partially upgraded state: Migration of api enabled by default (i.e. .Values.api.migration.enabled=true), which will lead to flask db upgrade action executed while Redis and PostgreSql were restarting, and api will possibly end up in partially upgraded state. To address the issue
  • temporarily turn off the migration upon upgrading to this release and execute the api upgrade afterwards, or
  • resume flask db upgrade process if it ends up in the partially upgrade state by restarting api with migration enabled after Redis and PostgreSQL finishes the rolling restart: kubectl rollout restart deployment <api-deployment>

Full Changelog: dify-0.28.1...dify-0.29.0