Improve `deployment:` configuration

[mloiseleur]

Welcome!

• Yes, I've searched similar issues on GitHub and didn't find any.
• Yes, I've searched similar issues on the Traefik community forum and didn't find any.

What do you want to achieve with this Chart ?

The deployment section is an important config section of this Chart. It allows to define how Traefik will be deployed.

It can be confusing, mainly because parameters are split between deployment and other sections:

1. deployment.healthcheck* but readinessProbe + livenessProbe + startupProbe are not in deployment.
2. updateStrategy (not in deployment.)
3. volumes + additionalVolumeMounts (not in deployment.)
4. env + envFrom (not in deployment.)
5. hostNetwork (not in deployment.)
6. affinity, nodeSelector, tolerations, topologySpreadConstraints, priorityClassName (not in deployment.)
7. securityContext + podSecurityContext (not in deployment.)
8. resources (not in deployment.)
9. additionalArguments (not in deployment.)

Those upstream k8s parameters are spread across this Chart values.

The proposal here is that we can possibly expose directly in values the k8s upstream spec (with some exceptions where it does not make sense). It would simplify the values and align it with k8s upstream config.