Open danielmiehle opened 1 year ago
In terms of reusability / maximum profit of the helm-charts, I think it makes sense to a) separate the deployment of Core Components and Decentralized Components into different namespaces and b) be able to switch on/off the deployment of Core Components for a INT/PROD migration.
I am interesting in contributing in this issue, but I want to make sure I fully understand what is needed. You want to include the charts that are used in the Data Chain Kit from the IRS team in the umbrella helm chart, and you want the previously mentioned components to be separated into two namespaces Decentralised Components and Core Components?
Hey @MarkAshraf96 great to hear from you. We'd like to provide a helm chart to participants that want to setup a completely "local" Catena-X setup. This includes the core components as well as the "decentral" components augmenting a data provider and a data consumer.
I'd like to separate the components to two namespaces / two helm deployments to give developers and customers the chance to deploy the two component-groups separately (i.e. somebody wants to deploy only the decentral components).
Then I understand it right, and will start working on it. Should it also be as the tutorial with a shell script with boolean parameters to control which of the two component-groups to be installed, or separate shell script for each of them?
@danielmiehle, @gerbigf Mark will contribute within our engagement from ARENA2036.
In the context of our "data integration tutorial" we need an update of the current helm chart of the IRS Team. https://eclipse-tractusx.github.io/docs/kits/Data%20Chain%20Kit/Operation%20View
The "Data Integration Tutorial" provides step-by-step instructions on how data providers set up the required components to connect their company to the data space.
The updated helm chart must include the following services.
Decentralized components:
Core Components:
cc: @gerbigf @maximilianong @jzbmw