Skip to content
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

Add helm upgrade workflow #26

Closed
SebastianBezold opened this issue Aug 28, 2023 · 4 comments · Fixed by #27 or #92
Closed

Add helm upgrade workflow #26

SebastianBezold opened this issue Aug 28, 2023 · 4 comments · Fixed by #27 or #92

Comments

@SebastianBezold
Copy link
Contributor

The current Lint and Test Charts workflow should be enhanced by a helm upgrade step, that verifies, that an upgrade from the latest released Chart version to the current chart present in the repo is possible.

This is not blocking the current release for Tractus-X 3.2, since there was not knowledge-agents-edc release before anyways, but should be added for future checks.

@drcgjung
Copy link
Contributor

Yeah, problem here is the same as with chart testing: there is an external vault dependency in each of the EDC charts too which makes "kind" deployment unuseful (both planes would not start without vault). I will try to figure out how we could reach that with 29.12

@SebastianBezold
Copy link
Contributor Author

Ok. Is there at least one chart, that does only use open source dependencies? HashiCorp Vault for example should be integrateable as dependency of the chart and just deploy it together.

@drcgjung
Copy link
Contributor

Ok. Is there at least one chart, that does only use open source dependencies? HashiCorp Vault for example should be integrateable as dependency of the chart and just deploy it together.

In Principle yes, but the vault needs to be populated with a few reasonable secrets (valid certs and public keys, aes keys, ...)
I have not managed to find out how to do that with hashicorp chart, would take another week I guess ,sorry.
But I have a solution that at least proves that when following the documentation, it would work "nearly" out of the box (ct install on your machine, for example). I'll keep you up-to-date.
At least I found a problem in the dataplane test pod this way ,-)

@SebastianBezold
Copy link
Contributor Author

Reopening, because GitHub does not recognizes "not closes #26" :) just saw "closes #26".

To your point @drcgjung: Fair enough. I think this sounds like a "initcontainer might help here" solution. We can check that out after the current release phase

drcgjung added a commit to catenax-ng/tx-knowledge-agents-edc that referenced this issue Aug 31, 2023
…s. fixes helm tests for multiple dataplanes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants