BaselineFunction and Baseline objects are still available, but they do not serve any purpose other than smooth transition to the Autonomous Anomaly Detector (AAD) framework. If you have custom StackPacks that auto-create baselines, this is the last opportunity to remove baselines from templates and make transition to AAD. In release v4.5 baselines will be removed completely and templates using them will break.elasticsearch-exporter has been renamed to prometheus-elasticsearch-exporter. This means that any configuration for that subchart needs to use the new subchart key elasticsearch.prometheus-elasticsearch-exporter.*passwordMd5 field in the file based authentication has been renamed to passwordHash as it is now possible to use bcrypt type passwords.stackstate-admin, stackstate-power-user, stackstate-guest. Additionally, a new default role stackstate-platform-admin has been introduced.platformAdminGroup and adminGroup. Users in the group platformAdminGroup are limited to only platform management tasks, such as change database retention, clear database, clear caches and view logs. Users in the group adminGroup no longer have platform management permissions.platformadmin username for platform management instead of admin. The admin user remains functional and has full content management rights as before.platformAdmin group.BaselineFunction and Baseline objects are still available, but they do not serve any purpose other than smooth transition to the Autonomous Anomaly Detector (AAD) framework. If you have custom StackPacks that auto-create baselines, this is the last opportunity to remove baselines from templates and make transition to AAD. In release v4.5 baselines will be removed completely and templates using them will break.passwordMd5 field in the file based authentication has been renamed to passwordHash as it is now possible to use bcrypt type passwords.stackstate-admin, stackstate-power-user, stackstate-guest. Additionally, a new default role stackstate-platform-admin has been introduced.platformAdminGroup and adminGroup. Users in the group platformAdminGroup are limited to only platform management tasks, such as change database retention, clear database, clear caches and view logs. Users in the group adminGroup no longer have platform management permissions.authentication section in the file application_stackstate.conf. If your authentication section has adminGroups, powerUserGroups, guestGroups definitions like in the example below:xxxGroups = ${stackstate.authorization.xxxGroups} ["custom-role"] as shown in the example below.platformadmin username for platform management instead of admin. The admin user remains functional and has full content management rights as before.platformAdmin group.values.yaml, you will most likely need to also set the CPU limit for the same pod(s).Notify via slack for component health state change. (deprecated) and Notify via slack for view health state change.(deprecated)./etc/sts-agent/conf.d/dynatrace.d/conf.yaml the previous location was /etc/sts-agent/conf.d/dynatrace_topology.d/conf.yaml.Notify via slack for component health state change. (deprecated) and Notify via slack for view health state change.(deprecated)./etc/sts-agent/conf.d/dynatrace.d/conf.yaml the previous location was /etc/sts-agent/conf.d/dynatrace_topology.d/conf.yaml.stackstate.server.config or stackstate.api.config value that contains an authentication section in the values.yaml file(s) used for installation.values.yaml file. After that, the authentication section can be completely removed. If this results in an empty config value it can be removed as well.stackstate-server pod has been replaced by a number of separate pods. Custom configuration in values.yaml should be updated:stackstate.components.server.config should be moved to stackstate.components.viewHealth.config.stackstate.components.server.config should be moved to stackstate.components.api.config.stackstate.baseUrl has been added. This is the public URL of StackState (how StackState is reachable from external machines) and is exposed via the UI script API. The file values.yaml should be updated to include the new stackstate.baseUrl parameter. The old stackstate.receiver.baseUrl parameter has been deprecated and will be removed in a future release, however, when no stackstate.baseUrl is provided in StackState v4.2, the configured stackstate.receiver.baseUrl will be used instead.stackstate.web.baseUrl. This is the public URL of StackState (how StackState is reachable from external machines) and is exposed via the UI script API. You can manually create a system environment variable called STACKSTATE_BASE_URL or add the value manually as a string in the file application_stackstate.conf.stackstate. This is now stackstate.receiver.apiKey. This is now named apiKeys and should be a list in the format [${stackstate.receiver.key}, ${?EXTRA_API_KEY}].processes.kafkaToElasticsearch.topology-events.kafka.topics.sts_topology_events.