-
Notifications
You must be signed in to change notification settings - Fork 28
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
Update Helm Chart from IRS Team to Release 3.2 #14
Comments
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. |
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. |
@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
The text was updated successfully, but these errors were encountered: