Create a local version vs production

[alexnuttinck]

Is your feature request related to a problem? Please describe.

Get a local version to be able to run the FADI stack locally and a production version. It uses currently too much resources for the local version.

Describe the solution you'd like

Get two different values.yaml files, one for minikube, one for production.

We could also pass a value minikube.yaml file which configure the ressources used (RAMs, CPUs).

helm upgrade --install ${NAMESPACE} cetic/fadi -f ./values.yaml -f minikube.yaml --namespace ${NAMESPACE} --tiller-namespace tiller

Describe alternatives you've considered

Explain in the documentation how to use less/more resources.

[banzo]

Instead of maintaining 2 files, maybe we can use tags in the values.yml file

[Sellto]

In the spirit of defining a minimal FADI version, I think it would be appropriate to reduce the skills necessary to be able to use and test FADI. For example, Data persistence and/or the use of a loadbalancer are features that require a mastery of kubernetes rather than the tools offered in FADI.

I therefore propose that by default the persistence of data be deactivated and that the services be only one of these two types: NodePort or CluserIP.

Of course, this version should be completed by a series of documentation allowing users to choose the solutions to these different features offering the best user experience of FADI.