Reuse values between namespaces

This is the reorganization proposed by the application configuration change [2]

Note this also adapts the make swh-helm-diff to actually execute the diff in the files we are deploying [1].

This also adapts the graphql configmap to align it with other templates (which also to reuse some already defined values).

[1]

[swh] Generate config in production branch for environment staging...
Switched to branch 'reuse-values-between-namespaces'
[swh] Generate config in reuse-values-between-namespaces branch for environment staging...
Switched to branch 'production'
Your branch is ahead of 'origin/production' by 1 commit.
  (use "git push" to publish your local commits)
[swh] Generate config in production branch for environment production...
Switched to branch 'reuse-values-between-namespaces'
[swh] Generate config in reuse-values-between-namespaces branch for environment production...


------------- diff for environment staging -------------

No differences


------------- diff for environment production -------------

No differences

[2] k8s-clusters-conf!30 (merged)

added 1 commit

• c5c7a220 - production: Extract common values in swh/values/production/default.yaml

Compare with previous version

changed the description

added 1 commit

• b5b7bd15 - Make swh-helm-diff command work with the new architectured values

Compare with previous version

changed the description

added 1 commit

• cfa4a42a - Make swh-helm-diff command work with the new architectured values

Compare with previous version

added 1 commit

• a33dac7d - Make swh-helm-diff command work with the new architectured values

Compare with previous version

changed the description

mentioned in merge request k8s-clusters-conf!30 (merged)

It globally make sense to avoid duplication but I'm afraid it will add more complexity to understand and maintain the configuration.

For example, some blur is introduced. There is a couple of storage declarations in the default.yaml files that have no sense for the cassandra environment and it's clearly not simple to identify.

We're also losing the information of composition by moving the next-version configuration at the same level than the other configurations. Nothing indicates now that the next-version configuration is an override of the swh-cassandra environment and is not usable as it. We should at least keep the override directory level.

added 1 commit

• 155d53cd - Keep the override notion for the swh-cassandra-next-version namespace

Compare with previous version

approved this merge request

The deduplication gains are enough to use these changes. We'll see later if such indirections are still needed when the cassandra/postgresql environment will be merged

added 3 commits

• ee4ca8cf - production: Extract common values in swh/values/production/default.yaml
• 06ce19bc - Make swh-helm-diff command work with the new architectured values
• d72f22bf - Keep the override notion for the swh-cassandra-next-version namespace

Compare with previous version

merged

resolved all threads