[Help] PgBouncer NodeSelector

[clickersmudge]

Hi, I can't figure out how to configure PgBouncer to schedule on the the indicated node.

How to properly set the

# nodeSelector:
      # example: example

for Pgbouncer in Helm Chart?

[itay-grudev]

The Pooler deployment is managed by the operator, but you can pass in a template to override certain properties.

See pooler.template.

https://cloudnative-pg.io/documentation/1.23/cloudnative-pg.v1/#postgresql-cnpg-io-v1-PoolerSpec

[clickersmudge]

Thanks @itay-grudev

[clickersmudge]

Hi @itay-grudev

I'm trying

template:
  nodeSelector:
    architecture: x86

template:
    spec:
      containers:
        nodeSelector:
          architecture: x86

And some other combinations, but it doesn't work.

[itay-grudev]

If you follow the API documentation:

• https://github.com/cloudnative-pg/charts/blob/c664085cee5355596b4b18ebfceb71ec1a48fba1/charts/cluster/values.yaml#L297-L299
• https://cloudnative-pg.io/documentation/1.23/cloudnative-pg.v1/#postgresql-cnpg-io-v1-PoolerSpec
• https://cloudnative-pg.io/documentation/1.23/cloudnative-pg.v1/#postgresql-cnpg-io-v1-PodTemplateSpec
• https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.28/#podspec-v1-core

You will find, the correct configuration to be:

pooler:
  template:
    spec:
      nodeSelector:
        architecture: x86

[clickersmudge]

@itay-grudev You're right, and that's exactly what I've been doing since the beginning,

I use Argo CD. After adding the configuration there is a problem. Pooler not sync.

[itay-grudev]

Hmm. Then you might want to raise an issue in https://github.com/cloudnative-pg/cloudnative-pg/ for the use case of only overriding certain properties, if one doesn't exist already.