ci: Test helm chart upgrade process against version in main branch

[ppawlowski]

Description

This PR extends the helm chart verification process by adding the upgrade step to the workflow. As a result, the helm chart from the particular PR is used for the upgrade process against deployment created with the helm chart from the main branch.

Related Issue(s)

#315

Checklist

• I have read the contribution guidelines
• Suitable unit/system level tests have been added and they pass
• Documentation has been updated
  • Upgrade instructions
  • Configuration details
  • Concepts
• Changes flowforge.yml?
  • Issue/PR raised on FlowFuse/helm to update ConfigMap Template
  • Issue/PR raised on FlowFuse/CloudProject to update values for Staging/Production

Labels

• Backport needed? -> add the backport label
• Includes a DB migration? -> add the area:migration label

[github-actions]

node-red:2.2.3-main-linux-amd64 scan results

27 tests    0 ✅  0s ⏱️
 4 suites   0 💤
 1 files    27 ❌

For more details on these failures, see this check.

Results for commit 07b33cb.

[github-actions]

node-red:3.1.x-main-linux-amd64 scan results

3 tests   0 ✅  0s ⏱️
4 suites  0 💤
1 files    3 ❌

For more details on these failures, see this check.

Results for commit 07b33cb.

[github-actions]

node-red:3.0.2-main-linux-amd64 scan results

 1 files  4 suites   0s ⏱️
10 tests 0 ✅ 0 💤 10 ❌
11 runs  0 ✅ 0 💤 11 ❌

For more details on these failures, see this check.

Results for commit 07b33cb.

[github-actions]

file-server:main-linux-amd64 scan results

2 tests   0 ✅  0s ⏱️
6 suites  0 💤
1 files    2 ❌

For more details on these failures, see this check.

Results for commit 07b33cb.

[github-actions]

node-red:3.0.2-main-linux-arm64 scan results

 1 files  4 suites   0s ⏱️
10 tests 0 ✅ 0 💤 10 ❌
11 runs  0 ✅ 0 💤 11 ❌

For more details on these failures, see this check.

Results for commit 07b33cb.

[github-actions]

node-red:2.2.3-main-linux-arm64 scan results

27 tests    0 ✅  0s ⏱️
 4 suites   0 💤
 1 files    27 ❌

For more details on these failures, see this check.

Results for commit 07b33cb.

[github-actions]

node-red:3.1.x-main-linux-arm64 scan results

3 tests   0 ✅  0s ⏱️
4 suites  0 💤
1 files    3 ❌

For more details on these failures, see this check.

Results for commit 07b33cb.

[github-actions]

forge-k8s:main-linux-amd64 scan results

2 tests   0 ✅  0s ⏱️
4 suites  0 💤
1 files    2 ❌

For more details on these failures, see this check.

Results for commit 07b33cb.

[github-actions]

file-server:main-linux-arm64 scan results

2 tests   0 ✅  0s ⏱️
6 suites  0 💤
1 files    2 ❌

For more details on these failures, see this check.

Results for commit 07b33cb.

[github-actions]

forge-k8s:main-linux-arm64 scan results

2 tests   0 ✅  0s ⏱️
4 suites  0 💤
1 files    2 ❌

For more details on these failures, see this check.

Results for commit 07b33cb.

[hardillb]

Just to be clear here, what version is it going to do the upgrade from?

I think it is going to install main, then do the upgrade to the PR?

[ppawlowski]

Just to be clear here, what version is it going to do the upgrade from?

I think it is going to install main, then do the upgrade to the PR?

That is correct.
IMO that makes more sense than testing the upgrade against the published version because it will also test against changes waiting to be released in the main branch.

Additionally, a regular, fresh installation is also performed. Due to 2 values file used, this pipeline will execute chart installation 6 times.