Open throrin19 opened 1 year ago
Any news about that ? It's really annoying and block us to upgrade to latest chart version
We had a similar issue.
It looks like in https://github.com/timescale/helm-charts/commit/fd2f21a02a6c50c47ccaab3dc39bb89cf620d308#diff-3210395104e9712528afa7119350e6250761db18b886c36af3e1dc600733fcfaL464
they removed tpl
function, and now you have to define it using simple values like:
podAntiAffinity:
preferredDuringSchedulingIgnoredDuringExecution:
- weight: 100
podAffinityTerm:
topologyKey: "kubernetes.io/hostname"
labelSelector:
matchLabels:
app: "timescaledb"
release: "timescaledb"
cluster-name: "timescaledb"
- weight: 50
podAffinityTerm:
topologyKey: failure-domain.beta.kubernetes.io/zone
labelSelector:
matchLabels:
app: "timescaledb"
release: "timescaledb"
cluster-name: "timescaledb"
In summary, the current upgrade guide is either incorrect or lacks logic (missing tpl
processing affinity).
What happened?
When I try to upgrade to the latest version (0.33.1) from the version 0.27.5, I have this error :
Did you expect to see something different?
No error
How to reproduce it (as minimally and precisely as possible):
Just copy this data in the
affinity
section of thevalue.yaml
:Environment
Which helm chart and what version are you using? timescaledb-single 0.33.1
What is in your
values.yaml
?Kubernetes cluster kind:
EKS 1.22 managed by rancher