[question] Best practise for defining DSF based in cluster size and question about appTemplate examples

[psykidellic]

Please let me know if there is a better place to ask this question. I am trying to figure out the best to create DSFs where our cluster is basically based on cluster/resource sizes. Instead of having dev, staging, testing, production, we want to have: dev, small, medium, large, scale. The common difference between all will be clusters would be: replicaCount, affinity and resource section. Other the charts are self sufficient. Namespaces are same "appns" is same across all apps.

Given this some options I was thinking of is:

• Have one set of dev.yaml, staging.yaml etc and our ci/cd will pick up the right file. This means whenever we add a new microservice, all the XXXX.yaml has to be updated for the new app. This is similar to the first option that was suggested at: https://github.com/Praqma/helmsman/issues/440

• I could follow method like: https://github.com/Praqma/helmsman/blob/master/examples/appsTemplates/config/helmsman.yaml where i have one DSF with different version of apps. This would probably make that ONE FILE HUGE but it could be managed. What I could not understand from the above example is how a subset of apps are only applied e.f. testing or development. In that example, it seems all the apps from both group of testing and development would be applied or am I missing some critical part of the example? To me it feels like it can be solved by adding specific group to each app (dev/staging/testing/production) and then: helmsman apply -group dev helmsman.yaml. This way for a new microservice, the developer has to be update only one yaml file and just provide all the values.

[github-actions[bot]]

This issue has been marked stale due to an inactivity.