build: cern-magnum is packaged as two seperate helm charts

From discussion on !231 (closed), we have decided to package cern-magnum as two separate charts (one with only and another excluding the crds).

This is required as for when multiple dependencies with very large crds are enabled in cern-magnum installation breaks owning to us exceeding the 2MB secret limit for our helm release.

Hiding this change purley in the CI from a package / installation perspective provides the least intrusive approach (as it does not require restructuring or maintaining two `values.yaml` [one for crds and another for the umbrella chart], nor does it require complicated if gating around templates or crds). This is intended as a temporary solution until plans to migrate the management of cern-magnum as an applicationset in argo are planned for and completed later on in the year.

changed milestone to %R-2024-Q3-1

requested review from @rbritoda and @digaponc

assigned to @jmunday

changed the description

added 4 commits

• afdd8ccb...c65b4c9a - 3 commits from branch master
• 55027f3a - build: package cern-magnum as two seperate charts

Compare with previous version

marked this merge request as ready

changed title from Draft: cern-magnum is packaged as two seperate helm charts to build: cern-magnum is packaged as two seperate helm charts

mentioned in issue #93 (closed)

added A-service p2 labels

added 1 commit

• e5493f52 - build: package cern-magnum as two seperate charts

Compare with previous version

added 1 commit

• 4aa6b4ee - build: package cern-magnum as two seperate charts

Compare with previous version

approved this merge request

resolved all threads

added 1 commit

• 30c327b3 - update build_chart stage to run package.sh

Compare with previous version

reset approvals from @rbritoda by pushing to the branch

added 1 commit

• 58be5d88 - update build_chart stage to run package.sh

Compare with previous version

approved this merge request

mentioned in commit 116f22af

merged