no option to use an existing priorityClassName for posgres Pods or make podPriorityClassName value configurable

[antonmatsiuk]

Please, answer some short questions which should help us to understand your problem / question better?

• Which image of the operator are you using?: registry.opensource.zalan.do/acid/postgres-operator:v1.10.1
• Where do you run it: cloud (AWS, Azure)
• Are you running Postgres Operator in production?: yes
• Type of issue?: [Bug report]

In the current implementation there is no option to specify an existing priorityClassName for Postgres Cluster pods. The actual value for priorityClassName is set only for postgres-operator deployment.

In contrast, podPriorityClassName parameter designed for PostgreSQL cluster disrespects existing priority classes in a cluster and creates a new priority class with a static priority value. This makes using the podPriorityClassName parameter unusable in production clusters where priority classes are created and managed externally. If an existing priority class is specified under podPriorityClassName (podPriorityClassName:critical in the example below), Helm Chart throws the following error:

Helm upgrade failed: error while running post render on files: may not
        add resource with an already registered id:
        PriorityClass.v1.scheduling.k8s.io/critical.[noNs]

Solution: add additional create boolean flag to pod-priority-class to ignore its creation and to allow usage of existing external priority classes