doc(README): remove affinity example
This commit is contained in:
parent
38cdcfd58a
commit
4bdf3f8173
25
README.md
25
README.md
@ -140,31 +140,6 @@ helm install prometheus-fail2ban-exporter prometheus-exporters/prometheus-fail2b
|
||||
--set 'grafana.enabled=true'
|
||||
```
|
||||
|
||||
#### Avoid deploying on same node / bare metal host as PostgresDB
|
||||
|
||||
As a best practice, avoid running the fail2ban-exporter on the same node / bare-metal host as the PostgresDB. This is
|
||||
because if the fail2ban-exporter is running on the same node and this node fails, Prometheus can send an alert about the
|
||||
failure of the node or that the fail2ban-exporter cannot be reached. However, it is not possible to react based on the
|
||||
metrics that the fail2ban-exporter explicitly provides. Depending on the configuration of alerts, this may mean that the
|
||||
corresponding notifications are not sent to the right person or group of people.
|
||||
|
||||
The following example prevent the fail2ban-exporter from running on nodes with a PostgresDB. The PostgresDB nodes has an
|
||||
additional label `database=fail2ban`. The configuration is carried out in `values.yaml`.
|
||||
|
||||
```yaml
|
||||
deployment:
|
||||
affinity:
|
||||
nodeAffinity:
|
||||
preferredDuringSchedulingIgnoredDuringExecution:
|
||||
- weight: 100
|
||||
preference:
|
||||
matchExpressions:
|
||||
- key: database
|
||||
operator: NotIn
|
||||
values:
|
||||
- fail2ban
|
||||
```
|
||||
|
||||
## Parameters
|
||||
|
||||
### Global
|
||||
|
Loading…
Reference in New Issue
Block a user