separate configs #6
Conversation
|
the motivation here was to support different node pools and different volumes per access/data I think this is time to refactor to have almost ALL of the parameters being specified per data/access nodes |
There was a problem hiding this comment.
should be in the form of
accessNode:
service:
type: LoadBalancer
resources:
postgresql:
databases: # only for accessNode
parameters:
persistentVolume:
dataNode:
replicas: # only for dataNode
service: # not sure if needed here
resources:
postgresql:
parameters:
persistentVolume:
| accessNode: | ||
| service: | ||
| type: LoadBalancer | ||
|
|
||
| # Credentials used by PostgreSQL | ||
| credentials: | ||
| fromValues: true |
There was a problem hiding this comment.
should I also move these to each node ?
There was a problem hiding this comment.
aren't they belong to access node only ?
if so I guess they better stay here
There was a problem hiding this comment.
both access node and data node use the credentials
There was a problem hiding this comment.
ohh
well good question
not sure then :-)
|
will update chart repo after final approve. |
| accessNode: | ||
| service: | ||
| type: LoadBalancer | ||
|
|
||
| # Credentials used by PostgreSQL | ||
| credentials: | ||
| fromValues: true |
There was a problem hiding this comment.
aren't they belong to access node only ?
if so I guess they better stay here
charts/timescaledb-multinode/templates/statefulset-timescaledb-accessnode.yaml
Outdated
Show resolved
Hide resolved
charts/timescaledb-multinode/templates/statefulset-timescaledb-accessnode.yaml
Outdated
Show resolved
Hide resolved
charts/timescaledb-multinode/templates/statefulset-timescaledb-accessnode.yaml
Show resolved
Hide resolved
|
reverted affinityTemplate |
Added separate config for data node and access node.
Access node config according to:
https://docs.timescale.com/timescaledb/latest/how-to-guides/multi-node-setup/required-configuration/#multi-node-configuration