-
Notifications
You must be signed in to change notification settings - Fork 219
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #1673 from eclipse-ditto/ditto-331
prepare Ditto 3.3.1 bugfix release
- Loading branch information
Showing
2 changed files
with
63 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
60 changes: 60 additions & 0 deletions
60
documentation/src/main/resources/pages/ditto/release_notes_331.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,60 @@ | ||
--- | ||
title: Release notes 3.3.1 | ||
tags: [release_notes] | ||
published: true | ||
keywords: release notes, announcements, changelog | ||
summary: "Version 3.3.1 of Eclipse Ditto, released on 29.06.2023" | ||
permalink: release_notes_331.html | ||
--- | ||
|
||
This is a bugfix release, no new features since [3.3.0](release_notes_330.html) were added. | ||
|
||
## Changelog | ||
|
||
Compared to the latest release [3.3.0](release_notes_330.html), the following changes and bugfixes were added. | ||
|
||
### Changes | ||
|
||
None | ||
|
||
|
||
### Bugfixes | ||
|
||
This is a complete list of the | ||
[merged pull requests](https://github.com/eclipse-ditto/ditto/pulls?q=is%3Apr+milestone%3A3.3.1). | ||
|
||
#### [Fix blocking Akka dispatcher thread on WoT skeleton creation](https://github.com/eclipse-ditto/ditto/pull/1666) | ||
|
||
Ditto's [WoT integration](basic-wot-integration.html) did block the Akka dispatcher thread which could lead to deadlock | ||
situations when e.g. creating new twins based on a WoT ThingModel. | ||
|
||
This was solved and the complete WoT operations are now executed asynchronously. | ||
|
||
|
||
### Helm Chart | ||
|
||
The [Ditto Helm Chart](https://github.com/eclipse-ditto/ditto/tree/master/deployment/helm), which was enhanced and changed | ||
a lot for version 3.3.0, contained some configuration bugs which are also addressed with this bugfix release. | ||
|
||
|
||
#### [Fix that nginx's worker_processes setting 'auto' causes problems with workers having many CPUs](https://github.com/eclipse-ditto/ditto/pull/1667) | ||
|
||
Configure the "dittoui"'s nginx to only use 1 worker process, as it only serves static content. | ||
Add configuration option in the Helm chart `values.yaml` to configure the nginx's used worker_processes and default to 4 | ||
|
||
#### [Fix wrong config path for pulling devops and status password from helm values](https://github.com/eclipse-ditto/ditto/pull/1671) | ||
|
||
The devopsPassword and statusPassword were read from `.Values.gateway.devopsPassword` and `.Values.gateway.statusPassword`. | ||
In the `values.yaml` these two values were however located at different configuration levels. | ||
|
||
As a result, the two passwords werew always regenerated and the passed passwords were not used. | ||
|
||
#### [Configure queryReadConcern: "local" for ditto things-search by default](https://github.com/eclipse-ditto/ditto/pull/1672) | ||
|
||
The `readConcern` was by default configured to `"linearizable"` which however fails in a "single instance" MongoDB setup. | ||
Changed to be by default `queryReadConcern: "local"` with hint to configure otherwise for replicated MongoDB setups. | ||
|
||
#### [Support for ingress controller](https://github.com/eclipse-ditto/ditto/pull/1668) | ||
|
||
The Ditto Helm chart now supports to additionally deploy a (nginx-based) "Ingress controller", if configured. | ||
By default, the deployment of the Ingress controller is however disabled. |