The Minnesota release of EdgeX is the 12th community release by the Foundry and continues the trend of reliably producing releases since the project’s inception in 2017.
The main theme of Minnesota and EdgeX 3.0 is usability. In particular, the way the user configures and controls EdgeX has been significantly improved and saves the user time when developing and deploying EdgeX solutions.
Other key updates in this new major version include built-in microservice authentication and upgrades to the EdgeX APIs. This release will be the basis for EdgeX going forward and will lead to the next Long Term Support (LTS) version later this year.
The EdgeX Foundry 3.0 (Minnesota) release includes the following major changes and additions since EdgeX 2.3 (Levski):
Common and Simplified Configuration of the EdgeX Services
This is the new ability to now configure key settings of EdgeX (logging, telemetry, security, database and message bus settings, etc) in a single configuration location rather than needing to apply settings across multiple microservice manually
The new common configuration approach provides a layered strategy, where in one place, users can configure settings common to all services or those that should only apply to the application or device services
Simplify the File Formats used for EdgeX Configuration
In EdgeX v2, different services were configured by different file formats
To simplify the user experience, v3 consolidates to JSON or YAML only. The TOML format has been removed
Updated V3 APIs
This is a major release bump so the APIs are updated to include v3 endpoints. For more information see the EdgeX V3 Migration Guide
Microservice Authentication with Vault JSON Web Tokens (JWT)
When run in secure mode, the EdgeX microservices will now require an authentication token before they will respond to requests issued over the REST API
The EdgeX Secret Store (Vault) now provides the tokens for each service to invoke authenticated outgoing requests to the other EdgeX services
EdgeX Foundry 3.0 (Minnesota) is a major release and is therefore not backwards compatible with the previous EdgeX V2 releases.
For a more detailed description of the changes and updates to the EdgeX Minnesota release, please see Release Notes
To provide EdgeX Foundry consumers with a predictable foundation on which to base their commercial offerings, a goal of EdgeX Foundry is to outline key release themes at least 12 months in advance and to plan features to be delivered in each release 6 months in advance.
Release cadence is biannual, with targets of April and October for the release months.
The source code for all EdgeX releases can be accessed on GitHub. Release branches are tagged with the associated release name (e.g., Levski)