BIMI support and migrate the static core UI container into a node.js service be3c40c5e
This is a breaking change
Introduces BIMI (Brand Indicators for Message Identification) support
Migrates the static core UI from nginx to a dynamic Node.js-based service
BIMI requires a database to cache records and logos when the feature is enabled
Please check and adjust existing memory limits! The former nginx-based service had a lower memory demand to just serve static UI sources. The nodejs-based service needs more room to work; especially when enabling features like BIMI. The default is 256Mi (for both request and limit). By default, the helm chart starts two instances of the service. For just serving static files, you can go back to one instance.
See documentation for deployment and configuration details
JWKS support to core UI
This is another breaking change
The core UI service takes over the JWT issuing from Switchboard
The most important configuration changes are documented in a migration guide
As a customer I want to customize Whats New entries to match my own release cadence (AS-173)
Show visual indication and error message based on $Failed keyword (scheduled send or snooze)