Dependencies Connector & Knowledge Agents Kits

[drcgjung]

This is a placeholder for the topics appearing in the dependency session between the Connector & Agents Kits for release 24.03

• Dismissal of the agent-connector helm charts https://github.com/eclipse-tractusx/knowledge-agents-edc/tree/main/charts in favor to separate agent-plane helm chart (see Dedicated helm chart for the Dataplane only? knowledge-agents-edc#61)

  • Registering an additional plane when its pod has started
    • Either setup code in the extension OR
    • additional wget/curl commands on the pod
  • ct test (TRG5) needs a VAULT, a MIW, a keycloak ... will there be some support by tractusx-connector charts?
    • MXD mit Terraform

• Migration of the v2 Management APIs to the v3 Management APIs

  • There seems to have been a switch of "connectorId" and "providerId" between TX EDC Control-Plane 0.5.0 and 0.5.1?
  • What about the "StatusChecker" for particular asset types. This currently leads to non-FINISHED transfer processes in 0.5.1
    • do we need to extend the control plane to provide additional checkers OR
    • will this be configurable (like a property per address type)
    • will there be a default checker (NoopChecker or something)
  • Should we switch to EDR cache instead of callback (the first will not work with control-plane-memory)
  • Should we prefer a Data-Plane Proxy / Gateway approach versus Data-Plane Http Transfer
    • asynchronous API
    • decoupling of baseUrl and backend system

• Future of auth-jwt (guess its redundant in the meantime) , synch with approach of @ndr-brt

[drcgjung]

Feature "Simplify KA-EDC Deployment"

Benefit Hypothesis

• Maintaining three or more variants of the TX EDC charts is always behind the "state-of-the-art"
• Having a chart for the agent plane itself which can be plugged into an existing EDC umbrella is more practical

Beneficiaries

• any participant already deploying an EDC without agent
• any newly onboarding participant unsure which chart to use
• enablement providers who want to offer variants in a more easy fashion

Acceptance Criteria

• for each vault type, an agent-plane only chart which will register itself at the umbrella EDC
• samples for side-by-side deployment

Estimated Story Points:
10 SP

 

[drcgjung]

Feature "Upgrade to EDC 24.03"

Benefit Hypothesis

• no confusing deprecation warnings
• usage of the latest deployment features
• better integration & E2E performance

Beneficiaries

• all KA-EDC participants

Acceptance Criteria

• we do not use deprecated features, like the management/v2 anymore
• existing integration & E2E scenarios still work

Estimated Story Points:
10 SP