Figure out prod config separate from dev

[corneliusroemer]

We currently run many tools in explicit dev mode. E.g. keycloak, which might cause perf issues.

It's important we know which perf issues are due to dev settings and will disappear with prod and which remain nonetheless.

For this, we need to work out a prod config. This is a collection issue with pointers to sub-issues for each service that needs to be prepared for prod:

• Keycloak: Create keycloak prod configuration #962
• Use secure passwords/settings by default: Security hardening: use proper passwords by default and test accounts only when requested with flags #981

[theosanderson]

(My) strategy for kubernetes is that the default values.yaml should be the prod config, and anything we need for dev should be a diversion away from that (e.g. atm disabling some components). I'd suggest we try to keep that going forward i.e. we make changes that make this default config more prod-dy and we add extra dev options if needed.

[corneliusroemer]

Sounds good that by default we try to make things as proddy as possible as soon as possible and only dev-ify when necessary.

[theosanderson]

I think this is broadly complete