Anyone got any ideas of how to force the postgres chart used

Question

Anyone got any ideas of how to force the postgres chart used in the helm chart to deploy on a particular node pool Have tried this ``` postgresql postgresqlPassword nodeSelector <http cloud google com gke nodepool|cloud google com gke nodepool> some node pool```

Josh Greenhalgh · Answer

but doesn t seem to work

Mariia Kerimova · Answer

Hello Josh Can you try following ```postgresql postgresqlPassword primary nodeSelector some node pool``` And can you confirm that nodes have labels ` some node pool`

Josh Greenhalgh · Answer

Yep will give that a go

Josh Greenhalgh · Answer

Nope disappointed the node pool defo exists so thats not the issue

Josh Greenhalgh · Answer

I suppose this is a perfect opportunity to use an external db

Mariia Kerimova · Answer

Did you update the chart with nodeselector According to <https github com bitnami charts tree master bitnami postgresql|bitnami postgresql chart> nodeSelector should be set not globally but under `primary` or `readReplicas` So if you will update Prefect helm chart to to have postgresql primary nodeSelector with labels on your nodes it should work slightly smiling face

Mariia Kerimova · Answer

Also if you want to use your own external db you can set `useSubChart false` and provide `externalHostname` of your database

Josh Greenhalgh · Answer

Yeah I did try that in the past with the primary key and it doesn t seem to be getting through this is my values ``` postgresql postgresqlPassword ChhXvTjB9w primary nodeSelector $ google container node pool prefect fixed compute name prefectConfig logging level DEBUG hasura resources limits cpu 0 5 memory 512Mi requests cpu 0 25 memory 256Mi nodeSelector $ google container node pool prefect fixed compute name graphql image tag core 0 14 12 resources limits cpu 0 2 memory 128Mi requests cpu 0 2 memory 128Mi nodeSelector $ google container node pool prefect fixed compute name apollo apolloApiUrl http 4200 graphql resources limits cpu 0 15 memory 256Mi requests cpu 0 15 memory 256Mi nodeSelector $ google container node pool prefect fixed compute name ui resources limits cpu 0 5 memory 20Mi requests cpu 0 25 memory 10Mi image tag core 0 14 12 nodeSelector $ google container node pool prefect fixed compute name towel image tag core 0 14 12 resources limits cpu 0 5 memory 128Mi requests cpu 0 25 memory 64Mi nodeSelector $ google container node pool prefect fixed compute name ```

Josh Greenhalgh · Answer

But if I look at the actual pod it looks like this with no ref to the nodeselector ```apiVersion v1 kind Pod metadata creationTimestamp 2021 03 24T12 16 22Z generateName prefect server postgresql labels prefect server Helm postgresql controller revision hash prefect server postgresql 7f5946fd88 postgresql 9 3 4 role master prefect server postgresql 0 managedFields apiVersion v1 fieldsType FieldsV1 fieldsV1 f metadata f generateName f labels f f f f controller revision hash f f role f f ownerReferences k uid d45cceb2 b76b 4167 8f6e 368273d7c19f f apiVersion f blockOwnerDeletion f controller f kind f name f uid f spec f containers k name prefect server postgresql f env k name BITNAMI DEBUG f name f value k name PGDATA f name f value k name POSTGRES DB f name f value k name POSTGRES PASSWORD f name f valueFrom f secretKeyRef f key f name k name POSTGRES USER f name f value k name POSTGRESQL ENABLE LDAP f name f value k name POSTGRESQL ENABLE TLS f name f value k name POSTGRESQL INITSCRIPTS USERNAME f name f value k name POSTGRESQL PORT NUMBER f name f value k name POSTGRESQL VOLUME DIR f name f value f image f imagePullPolicy f livenessProbe f exec f command f failureThreshold f initialDelaySeconds f periodSeconds f successThreshold f timeoutSeconds f name f ports k containerPort 5432 protocol TCP f containerPort f name f protocol f readinessProbe f exec f command f failureThreshold f initialDelaySeconds f periodSeconds f successThreshold f timeoutSeconds f resources f requests f cpu f memory f securityContext f runAsUser f terminationMessagePath f terminationMessagePolicy f volumeMounts k mountPath dev shm f mountPath f name k mountPath docker entrypoint initdb d f mountPath f name f dnsPolicy f enableServiceLinks f hostname f restartPolicy f schedulerName f securityContext f fsGroup f subdomain f terminationGracePeriodSeconds f volumes k name custom init scripts f configMap f defaultMode f name f name k name data f emptyDir f name k name dshm f emptyDir f medium f sizeLimit f name manager kube controller manager operation Update time 2021 03 24T12 16 22Z apiVersion v1 fieldsType FieldsV1 fieldsV1 f status f conditions k type ContainersReady f lastProbeTime f lastTransitionTime f status f type k type Initialized f lastProbeTime f lastTransitionTime f status f type k type Ready f lastProbeTime f lastTransitionTime f status f type f containerStatuses f hostIP f phase f podIP f podIPs k ip 10 32 1 2 f ip f startTime manager kubelet operation Update time 2021 03 24T12 16 36Z name prefect server postgresql 0 namespace prefect ownerReferences apiVersion apps v1 blockOwnerDeletion true controller true kind StatefulSet name prefect server postgresql uid d45cceb2 b76b 4167 8f6e 368273d7c19f resourceVersion 11181483 selfLink api v1 namespaces prefect pods prefect server postgresql 0 uid ad82aaf5 9869 42b8 b5a6 8fe4f438045d spec containers env name BITNAMI DEBUG value false name POSTGRESQL PORT NUMBER value 5432 name POSTGRESQL VOLUME DIR value bitnami postgresql name POSTGRESQL INITSCRIPTS USERNAME value postgres name PGDATA value bitnami postgresql data name POSTGRES USER value prefect name POSTGRES PASSWORD valueFrom secretKeyRef key postgresql password name prefect server postgresql name POSTGRES DB value prefect name POSTGRESQL ENABLE LDAP value no name POSTGRESQL ENABLE TLS value no image imagePullPolicy IfNotPresent livenessProbe exec command bin sh c exec pg isready U prefect d dbname=prefect h 127 0 0 1 p 5432 failureThreshold 6 initialDelaySeconds 30 periodSeconds 10 successThreshold 1 timeoutSeconds 5 name prefect server postgresql ports containerPort 5432 name tcp postgresql protocol TCP readinessProbe exec command bin sh c e | exec pg isready U prefect d dbname=prefect h 127 0 0 1 p 5432 f opt bitnami postgresql tmp initialized || f bitnami postgresql initialized failureThreshold 6 initialDelaySeconds 5 periodSeconds 10 successThreshold 1 timeoutSeconds 5 resources requests cpu 250m memory 256Mi securityContext runAsUser 1001 terminationMessagePath dev termination log terminationMessagePolicy File volumeMounts mountPath docker entrypoint initdb d name custom init scripts mountPath dev shm name dshm mountPath var run secrets kubernetes io serviceaccount name default token 5c9rd readOnly true dnsPolicy ClusterFirst enableServiceLinks true hostname prefect server postgresql 0 nodeName gke ecaa gke cluster prefect jobs fi 22bd82a9 2xld priority 0 restartPolicy Always schedulerName default scheduler securityContext fsGroup 1001 serviceAccount default serviceAccountName default subdomain prefect server postgresql headless terminationGracePeriodSeconds 30 tolerations effect NoExecute key operator Exists tolerationSeconds 300 effect NoExecute key operator Exists tolerationSeconds 300 volumes configMap defaultMode 420 name prefect server postgresql init scripts name custom init scripts emptyDir medium Memory sizeLimit 1Gi name dshm emptyDir name data name default token 5c9rd secret defaultMode 420 secretName default token 5c9rd status conditions lastProbeTime null lastTransitionTime 2021 03 24T12 16 22Z status True type Initialized lastProbeTime null lastTransitionTime 2021 03 24T12 16 36Z status True type Ready lastProbeTime null lastTransitionTime 2021 03 24T12 16 36Z status True type ContainersReady lastProbeTime null lastTransitionTime 2021 03 24T12 16 22Z status True type PodScheduled containerStatuses containerID image bitnami postgresql 11 9 0 debian 10 r1 imageID lastState name prefect server postgresql ready true restartCount 0 started true state running startedAt 2021 03 24T12 16 30Z hostIP 10 154 0 10 phase Running podIP 10 32 1 2 podIPs ip 10 32 1 2 qosClass Burstable startTime 2021 03 24T12 16 22Z ```

Josh Greenhalgh · Answer

The selectors on the other services all work as expected and its the same node pool so shrug skin tone 6

Mariia Kerimova · Answer

Oh I see Your postgres uses bitnami helm chart 9 3 4 version Current version is 11 9 0 In 9 3 4 you can set nodeSelector like this ```postgresql postgresqlPassword master nodeSelector <http cloud google com gke nodepool|cloud google com gke nodepool> some node pool``` In version 10 terms `master` and `slave` were renamed to `primary` and `readReplicas`

Josh Greenhalgh · Answer

Ahh ok thanks Probably good idea to bump the bitnami chart too yeah

Mariia Kerimova · Answer

Yes even though I don t see other breaking changes I can t guarantee that there are no other caveats I would bump and test it thoroughly

Josh Greenhalgh · Answer

Cool will do thanks