Release 5.2.1
Removing the Legacy Notification Service
The legacy notification service (notificationsvc) has been replaced by the platform notification service (platform-notificationsvc) and is removed from the DT Platform Helm Chart in Release 5.2.1. Its web deployment, worker deployment, migration job, service, and HTTPRoute are no longer rendered by the chart. This includes the following changes:
- Removing the
NOTIFICATIONSVC_DEFAULT_PASSWORD,POSTGRES_NOTIFICATIONSVC_PASSWORD, andREDIS_NOTIFICATIONSVC_PASSWORDenvironment variables, thenotificationsvc-internalsecret (managed by the Helm chart and removed automatically), and thenotificationsvc-externalsecret (managed by the administrator and removed through a separate process). - Removing the
notificationsvcdbPostgreSQL database and thenotificationsvcPostgreSQL and Redis users. These are managed outside the Helm chart and should be decommissioned by the administrator once no data needs to be retained. - Removing all settings in
values.yamlof the DT Platform Helm Chart.
config.internal.notificationsvc.*
config.external.postgres.database.notificationsvc.*
config.external.postgres.user.notificationsvc.*
config.external.redis.user.notificationsvc.*
ingress.notificationsvc.*
service.notificationsvc.*
deployment.notificationsvc-web.*
deployment.notificationsvc-worker.*
job.notificationsvc-migrations.*
secretDef[name="NOTIFICATIONSVC_DEFAULT_PASSWORD"]
secretDef[name="POSTGRES_NOTIFICATIONSVC_PASSWORD"]
secretDef[name="REDIS_NOTIFICATIONSVC_PASSWORD"]
- Removing
notificationsvc-externalfrom theincludelist of the sharedSMTP_DEFAULT_PASSWORDsecret. The platform notification service continues to use this secret.