Feat: Moving helm values from product-semantics to tractusx repository

[agg3fe]

Description

Since product-semantics in catenax-ng will shutdown soon, so its important to move helm values from product-semantics to tractusx repository.

Related issue: #422

Pre-review checks

Please ensure to do as many of the following checks as possible, before asking for committer review:

• DEPENDENCIES are up-to-date. Dash license tool. Committers can open IP issues for restricted libs.
• Copyright and license header are present on all affected files

[agg3fe]

@evegufy Hi Evelyn, as we discussed last week, I am moving the helm values to tractusx repo. something similar to what you have done in portal repo. You can review my PR and let me know your thoughts.

[evegufy]

I'd change the section in the notice in the following way:

Test Environments

The project contains deployment configuration specific to hosted test environments needed for integration and end-to-end testing. This configuration is maintained within the environments directory.

Generally, now that the association environments are coming up, I was thinking to rework the folder structure in the following manner.

project
│   README.md
│
└─── environments
 └─── association
    └─── argocd-app-templates
        │   file111.yaml
        │   file112.yaml
    └─── helm-values
        │   file111.yaml
        │   file112.yaml
 └─── consortia
    └─── argocd-app-templates
        │   file111.yaml
        │   file112.yaml
    └─── helm-values
        │   file111.yaml
        │   file112.yaml

Could you please change that accordingly?
It's fine that you have for now just the consortia subfolder, which should be removed once the move to the association environment was completed.

[agg3fe]

I'd change the section in the notice in the following way:

Test Environments

The project contains deployment configuration specific to hosted test environments needed for integration and end-to-end testing. This configuration is maintained within the environments directory.

Generally, now that the association environments are coming up, I was thinking to rework the folder structure in the following manner.

project
│   README.md
│
└─── environments
 └─── association
    └─── argocd-app-templates
        │   file111.yaml
        │   file112.yaml
    └─── helm-values
        │   file111.yaml
        │   file112.yaml
 └─── consortia
    └─── argocd-app-templates
        │   file111.yaml
        │   file112.yaml
    └─── helm-values
        │   file111.yaml
        │   file112.yaml

Could you please change that accordingly? It's fine that you have for now just the consortia subfolder, which should be removed once the move to the association environment was completed.

I have modified the notice file and also the folder structure.

[tunacicek]

The files in consortia/argocd-app-templates are the same like in association. I think we can remove the files here

[agg3fe]

The whole consortia folder will be removed as soon as consortium ends. so this is temporarily placed here.
Will need to refer to association folder from argoCD.

[tunacicek]

This is pointing to main and sync with main. Does it make sense to introduce chart.yml etc. to define helm versions?
Otherwise, it is not possible to define a released Helm version, as it always uses the Helm version from main.

[agg3fe]

Yes I will change this to tagged versions instead of main branch.

[tunacicek]

i think we need to change the way it is.
Because this script runs one time to create the app.
If we keep it like this (main), the newest helm which is defined will be taken.
If you change to a tag - How it looks when we want to deploy a newer helm version?