delete harbor-postgres Kustomization after migration to CNPG

This is a follow-up to !3633 (merged), to address Deletion of old harbor postgres DB after integr... (#2067 - closed).

The idea is simply to leverage the "2-step" uprgade framework to ensure that after the first iteration where the migration to the CNPG DB is done, another sylva-units iteration happens where the old harbor-postgres Kustomization won't be enabled anymore, resulting in its deletion.

Confirmation that this gets the work done:

• Kustomization/sylva-units-status state changed: Additional reconciliation requested in https://gitlab.com/sylva-projects/sylva-core/-/jobs/14667523685/viewer#L9258
• https://gitlab.com/sylva-projects/sylva-core/-/jobs/14667523685/artifacts/external_file/management-cluster-dump/Kustomizations.summary.txt
  • -> no harbor-postgres Kustomization in sylva-system

💡 this MR give a way to have CI-testing to confirm that the removal of the old happens without problematic side-effect

CI configuration

Below you can choose test deployment variants to run in this MR's CI.

Click to open to CI configuration

Legend:

Icon	Meaning	Available values
☁️	Infra Provider	capd, capo, capm3
🚀	Bootstrap Provider	kubeadm (alias kadm), rke2, okd, ck8s
🐧	Node OS	ubuntu, suse, na, leapmicro
🛠️	Deployment Options	Deployment option list and description
🎬	Pipeline Scenarios	Available scenario list and description
🟢	Enabled units	Any available units name, by default apply to management and workload cluster. Can be prefixed by mgmt: or wkld: to be applied only to a specific cluster type
🔴	Disabled units	Any available units name, by default apply to management and workload cluster. Can be prefixed by mgmt: or wkld: to be applied only to a specific cluster type
🏗️	Target platform	Can be used to select specific deployment environment Available platform list and description
⚡	Pipeline control	autorun, manual or blocking. Can be used to override global config and start a deployment pipeline the required way

• 🎬 preview ☁️ capd 🚀 kadm 🐧 ubuntu

• 🎬 preview ☁️ capo 🚀 rke2 🐧 suse

• 🎬 preview ☁️ capm3 🚀 rke2 🐧 ubuntu

• ☁️ capd 🚀 kadm 🛠️ light-deploy 🐧 ubuntu

• ☁️ capd 🚀 rke2 🛠️ light-deploy 🐧 suse

• ☁️ capo 🚀 rke2 🟢 harbor 🎬 upgrade-from-release-1.6 🛠️ ha 🐧 suse

• ☁️ capm3 🚀 rke2 🟢 harbor 🎬 upgrade-from-release-1.6 🛠️ ha 🐧 suse

Global config for deployment pipelines

• autorun pipelines
• allow failure on pipelines
• record sylvactl events

Notes:

• Enabling autorun will make deployment pipelines to be run automatically without human interaction
• Disabling allow failure will make deployment pipelines mandatory for pipeline success.
• if both autorun and allow failure are disabled, deployment pipelines will need manual triggering but will be blocking the pipeline

Be aware: after configuration change, pipeline is not triggered automatically. Please run it manually (by clicking the run pipeline button in Pipelines tab) or push new code.