chapter: Timzone (Package tzdata) setting

text:
You can set the timezone in the PODs by
- per Component:
`timezone: "Europe/Berlin"`
- per Instance:
`global.timezone: "Europe/Berlin"`
- per Environment:
`global.environment.timezone: "Europe/Berlin"`
This is compatible to the *tzdata* package. If the image you use uses a different timezone package und thus a environment variable other than `TZ`, you can also set any global ENV Variables by
- per Component:
`env.TZ: "Europe/Berlin"`
- per Instance:
`global.env.TZ: "Europe/Berlin"`
- per Environment:
`global.environment.env.TZ: "Europe/Berlin"`
If you do not set the timezone, **it defaults to `Europe/Berlin`** and the `TZ` env variable.


chapter: Placement

text:
The inter pod anti-affinity is set by default to avoid a placement of two replicas of the same set to one node.
This is done for nappl, rs, ilm, cmis, web, webdav based on instance, component and type
For the nstl, this is handled by instance and type only, since the nstl does not use replicas and we are using different sets to ensure HA.
Additionally, you can set the scheduler to avoid or prefer specific nodes by setting *tolerations* and use *nodeSelectors*:
- `tolerations`
List of Kubernetes [`tolerations`](https://kubernetes.io/docs/concepts/scheduling-eviction/taint-and-toleration/) to add to the component
- `nodeSelector`
Kubernetes [`nodeSelector`](https://kubernetes.io/docs/concepts/configuration/assign-pod-node/#nodeselector) to add to the component


chapter: Maintenance Mode

text:
You can start the component in *Maintenance Mode*, starting the pod without starting the service, providing the possibility to gain access to the container to perform recovery tasks that need to be done offline.
In order to do this:
- All *waitFor* definitions are ignored
- All *Health Checks* are ignored
- The container starts in idle


chapter: minReplicaCountType

text:
If you set minReplicaCountType, a podDesruptionBudget will be created with this value as minReplicaCount. It will select pods based on the type of this component.
This is used for components, that do **not** support multiple replicas (for example sharepoint or storage layer).
If the component does in fact support replicas, it is better to use `minReplicaCount` instead.
Also pay attention to only set this on one ReplicaSet of this type, not all.
Please refer to the HA sample for more information.