Tractus-X 24.08
The overarching project is guided by https://catena-x.net and all development work is covered in https://eclipse-tractusx.github.io.
All notable changes on the overarching level are documented in this file. Refer to component repositories for specific content, changelog and documentation.
The format is based on Keep a Changelog.
Tractus-X operates on YY.0M.MICRO Calendar Versioning for overarching, quarterly Releases. Semantic Versioning remains unchanged for all components.
[24.08] - 2024-08-05
Added
| Component | Helm Chart (s) | App-/KIT Version (s) |
|---|---|---|
| Knowledge Agents AAS Bridge | aas-bridge: 1.13.7 | 1.13.7 |
| Supply Chain Disruption Notifications Kit | n/a | 1.0.0 |
| SSI Authority & Schema Registry | ssi-asr: 1.0.0 | 1.0.0 |
Updated
Unchanged, untested
| Component | Helm Chart (s) | App-/KIT Version (s) |
|---|---|---|
| Country Risk | country-risk: 4.0.2 | 1.3.1 |
Incompatible
| Component | Helm Chart (s) | App-/KIT Version (s) |
|---|---|---|
| Managed Identity Wallet (MIW) | managed-identity-wallet: 0.5.0 | v0.5.0 |
Known Knowns
:::note
For known knowns of unchanged/untested components, please refer to previous changelog(s)
:::
- Relevant components and interfaces developed considering Gaia-X Trust Framework - 22.10
- Connection to an external Clearing House service for the entire Catena-X ecosystem is required. The Gaia-X compliance service should generally be capable of recognizing all companies that are able to register with the Catena-X Portal.
- This Tractus-X release does not include a Managed Identity Wallet (MIW). The development team decided on a temporary bridging solution, based on a commercial application, to test and ship Release 24.08. Without implementing this interim solution, participants will not be able to fully utilize this Tractus-X release in consequence.
- For E2E Testing, the 1.2.0 of the SSI DIM Middle Layer was used - this component is FOSS but the currently used wallet (see previous item) is not.
- Documentation content (e.g. architecture, manuals etc) and folder structure have not explicitly been checked for this Release, as relevant TRGs are not yet in force. The vast majority of components are evolutions of previous Releases, with a thorough review undergone. This leads to a high confidence in the quality of existing documentation within the product repositories.
- FOSS components developed and pre-tested to TRL6 with artificial test data only
- No crosscheck of functionality in verification environment
- No execution of Load-, Performance- or Penetration Tests
- No assignment of Export Control Classification Numbers (ECCN) to FOSS components
- GeoBlocking recommended for Operations (GBaaS)
- Security concept (overall) recommended for Operations
- Listed components in "Unchanged, untested" category were not verified in combination with the current release package and are only compatible with Catena-X standards as specified. Use at your own risk at this time.
- Listed components in "Incompatible" category are not compatible with the current release package and the latest standards.
- BPDM has some Known Knowns regarding Portal integration listed in detail here
- BPDM standard configuration not compatible with Portal's Central-IDP configuration
- Portal's Partner Network page does not currently show business partner member data due to an authorization issue
- Currently not possible to add company's site and address business partners over the Portal due to authorization issue
- Security concern about exposed technical users when subscribing BPDM services over the Portal
- DTR introduces the DTR-EDC Access Control extension. The goal of this EDC extension is to enforce authorized access to submodel implementations according to AAS and Catena-X concluded contracts. It is a Maven artifact that can be used for building their own EDC dataplane image with the extension. For more details, see here.
Runtime
The release has been tested
- on Kubernetes versions:
1.28.9 - with PostgreSQL versions:
15
Note: Tractus-X EDC has been tested on both Postgresql versions: 15.x and 16.x
Using helm with central helm registry
You can search all released helm charts with the following commands:
helm repo add tractusx-dev https://eclipse-tractusx.github.io/charts/dev
helm repo update tractusx-dev
helm search repo tractusx-dev --versionsFor installation details, please see the referenced Repositories / Releases.