staging/staging-next-version: Make deployments independent
So the latter does not depend on the former.
They are actually independent from each other but the current chaining in deployment makes them dependent (from argocd's point of view).
Which makes the maintenance regularly confusing.
The development will happen in the swh-next-version branch and be merged in staging/production at the end.
Plan:
- Stop next-version from running
- argocd: Install sync window to only trigger sync when ready
- swh-charts: Rename swh-charts:/swh/values/staging/overrides/swh-cassandra-next-version.yaml to swh-charts:/swh/values/staging/next-version.yaml [1]
- k8s-cluster-config: Adapt next-version-swh-cassandra-applicationset.yaml value files to load
- (ongoing)Deploy and fix what's breaking (because it's missing some used-to-be-provided-configuration-by-swh-cassandra-ns-config).
- swh-charts: Cleanup unnecessary override (which disabled whatever was enabled by the staging swh-cassandra.yaml file but is no longer necessary in next-version)
- Merge in staging/production
[1] As decided orally a while back.