-
Notifications
You must be signed in to change notification settings - Fork 1
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 support for release CRs #290
Conversation
Note As this is a draft PR no triggers from the PR body will be handled. If you'd like to trigger them while draft please add them as a PR comment. |
This has been tested on |
There were differences in the rendered Helm template, please check! Output
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
overall looks good to me 👍
I suppose we need to add this to the cluster test values as my current E2E is failing
|
Towards: giantswarm/roadmap#3646
Aligning with CAPA/CAPZ Releases.
Since it's a breaking change I added a note to the changelog.
From now on we would fetch all app / helmrelease versions from the Release CR in
releases
repo forvsphere
.This has been tested on
gcapverde
, I applied the first release starting with v27, see giantswarm/releases#1422Trigger e2e tests
/run cluster-test-suites