You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
## Use taintsand tolerations for dedicated PostgreSQL nodes
520
+
## Use taints, tolerations and node affinity for dedicated PostgreSQL nodes
521
521
522
522
To ensure Postgres pods are running on nodes without any other application pods,
523
523
you can use [taints and tolerations](https://kubernetes.io/docs/concepts/configuration/taint-and-toleration/)
@@ -531,6 +531,28 @@ spec:
531
531
effect: NoSchedule
532
532
```
533
533
534
+
If you need the pods to be scheduled on specific nodes you may use [node affinity](https://kubernetes.io/docs/tasks/configure-pod-container/assign-pods-nodes-using-node-affinity/)
535
+
to specify a set of label(s), of which a prospective host node must have at least one. This could be used to
536
+
place nodes with certain hardware capabilities (e.g. SSD drives) in certain environments or network segments,
537
+
e.g. for PCI compliance.
538
+
539
+
```yaml
540
+
apiVersion: "acid.zalan.do/v1"
541
+
kind: postgresql
542
+
metadata:
543
+
name: acid-minimal-cluster
544
+
spec:
545
+
teamId: "ACID"
546
+
nodeAffinity:
547
+
requiredDuringSchedulingIgnoredDuringExecution:
548
+
nodeSelectorTerms:
549
+
- matchExpressions:
550
+
- key: environment
551
+
operator: In
552
+
values:
553
+
- pci
554
+
```
555
+
534
556
## How to clone an existing PostgreSQL cluster
535
557
536
558
You can spin up a new cluster as a clone of the existing one, using a `clone`
0 commit comments