Allow charts to have customized liveness and readiness probes

[keyvaann]

Allow custom application images to define their own health checks instead of using the hard coded one.

[github-actions]

Great PR! Please pay attention to the following items before merging:

Files matching charts/*/values.yaml:

• Is the PR adding a new container? Please reviewer, add it to the models (internal process)
• Is the PR adding a new parameter? Please, ensure it’s documented in the README.md

This is an automatically generated QA checklist based on modified files.

[blootsvoets]

I'm wondering a bit about the customLivenessProbe syntax, is this something that Bitnami also does? It's not blocking though, so go ahead and merge.

[blootsvoets]

It would be good to clarify that all livenessProbe values are disregarded if this custom livenessProbe is defined. Alternatively, just add the httpGet command to livenessProbe and users can override it, so the yaml is just copied to the deployment?

[keyvaann]

The syntax is copied from Bitnami, since I'd like to be compatible with their syntax and rather not change things unless necessary.
The syntax is a simple toYaml statement custom probe is specified: livenessProbe: {{- .Values.customLivenessProbe | toYaml | nindent 12 }}
Each service uses a different way to do the healthcheck, most use exec, some httpGet and some tcpSocket, adding only httpGet wouldn't fit all of them.