You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
While deploying tracetest with the cli tooling on a arm64 based cluster the deployment fails due to the bitnami postgres image (14.6.0-debian-11-r13) currently used not support arm64. Leaving postgres in a crash loop.
Browser (please complete the following information):
N/A
Additional context
Nodes are running on ARM64
Ubuntu 23.04
k3s
The text was updated successfully, but these errors were encountered:
@ornell sorry to hear about this issue. It seems that the chart version we're using doesn't support arm architectures, but there are others that do. I'll start working on updating the chart, but as a temporary measure, you can manually upgrade the pod. These commands assumes you're using the tracetest default namings, mainly tracetest namespace and tracetest as the chart install name:
# replace the image name in the stateful set
kubectl get statefulset -n tracetest tracetest-postgresql -o yaml | sed -e 's/14.6.0-debian-11-r13/14.7.0-debian-11-r29/g' | kubectl apply -n tracetest -f -
# optionally force delete the pod to speed up recreation
kubectl delete pod -n tracetest tracetest-postgresql-0 --grace-period=0 --force
This should help you start the service while we work on an actual more permanant fix. I'll keep you updated.
@ornell I wanted to let you know that we already updated our helm chart to use this version with ARM support. You can reinstall (or helm upgrade) tracetest and it shuold work now.
It'd be great if you could test the fix and confirm it's working, since I don't have access to a linux arm machine.
Describe the bug
While deploying tracetest with the cli tooling on a arm64 based cluster the deployment fails due to the bitnami postgres image (14.6.0-debian-11-r13) currently used not support arm64. Leaving postgres in a crash loop.
Browser (please complete the following information):
Additional context
The text was updated successfully, but these errors were encountered: