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
Allow configuring pod priority globally and per cluster. (zalando#353)
* Allow configuring pod priority globally and per cluster.
Allow to specify pod priority class for all pods managed by the operator,
as well as for those belonging to individual clusters.
Controlled by the pod_priority_class_name operator configuration
parameter and the podPriorityClassName manifest option.
See https://kubernetes.io/docs/concepts/configuration/pod-priority-preemption/#priorityclass
for the explanation on how to define priority classes since Kubernetes 1.8.
Some import order changes are due to go fmt.
Removal of OrphanDependents deprecated field.
Code review by @zerg-junior
Copy file name to clipboardExpand all lines: docs/reference/operator_parameters.md
+25-12Lines changed: 25 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -116,10 +116,15 @@ configuration they are grouped under the `kubernetes` key.
116
116
option. If not defined, a simple definition that contains only the name will be used. The default is empty.
117
117
118
118
***pod_service_account_role_binding_definition**
119
-
This definition must bind pod service account to a role with permission sufficient for the pods to start and for Patroni to access k8s endpoints; service account on its own lacks any such rights starting with k8s v1.8. If not excplicitly defined by the user, a simple definition that binds the account to the operator's own 'zalando-postgres-operator' cluster role will be used. The default is empty.
119
+
This definition must bind pod service account to a role with permission
120
+
sufficient for the pods to start and for Patroni to access k8s endpoints;
121
+
service account on its own lacks any such rights starting with k8s v1.8. If
122
+
not excplicitly defined by the user, a simple definition that binds the
123
+
account to the operator's own 'zalando-postgres-operator' cluster role will
0 commit comments