-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs(release preparation): prepare changelog for release 24.12 #38
Conversation
@ds-hzimmer could you check if the Kubernetes version is correct and add the PostgreSQL version. |
@lgblaumeiser Is this still correct, or has the Tractus-X EDC already been tested on another Postgresql version?
|
The INT environment (Azure cx-int-aks) is running on Kubernetes 1.28.9 |
SD Factory should be moved to updated table. Functionality tested within Portal regression tests (onboarding self description step, connectors, etc.). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The known knowns from the previous release should be checked if they apply still to this release.
I know the following is still relevant:
- 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.
As well as the following updated note:
- For E2E Testing, the 2.1.1 of the SSI DIM Middle Layer was used - this component is FOSS but the currently used wallet (see previous item) is not.
@nicoprow the following should be removed, right?
- BPDM has some Known Knowns regarding Portal integration listed in detail here
The following is still relevant (was heavily discussed in the last months):
- Security concern about exposed technical users when subscribing BPDM services over the Portal
but the link to the according sig-release issue could be added sig-release#987
Just as a note, the following are solved by now:
- 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
Thank you @evegufy |
Hi @ther3sa, the released helm chart refers to Postgresql 15.2.1. But internal testing of EDC is done using version 16.4. So I can confirm 16.4. As I would assume, that during end-to-end testing people used 15.2.1 as indicated by the helm charts, I would fo that far that we can expect this statement to be valid |
okay thank you :) |
Right, the only Known-knowns are the exposed service accounts. The updated documentation of BPDM takes that into account: https://github.com/eclipse-tractusx/bpdm/blob/release/6.2.x/docs/architecture/11_Risks_And_Technical_Debts.md#exposed-technical-users-on-portal So I would also only keep the point you wrote: "Security concern about exposed technical users when subscribing BPDM services over the Portal" |
Sanity Check
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Description
PR to collaboratively work on the Changelog for R24.12
[24.12] - 2024-12-02
Implemented features can be found here
Updated
sharedidp: 4.0.0
provisioning-agent: 1.14.24
conforming-agent: 1.14.24
matchmaking-agent: 1.14.24
provisioning-agent: 1.14.24
conforming-agent: 1.14.24
matchmaking-agent: 1.14.24
frontend: 2.3.0
backend: 2.3.0
assets: 2.3.0
Known Knowns
Runtime
The release has been tested
1.28.9
15.2.1.
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:
For installation details, please see the referenced Repositories / Releases.
Pre-review checks
Please ensure to do as many of the following checks as possible, before asking for committer review: