Solved:
Using the helm chart from here: https://github.com/jmferrer/taiga-docker/tree/taiga6-helm-chart/helm-chart
Values are not documented in the README.md, so I just took the relevant values from the values.yml and modified them.
@yami
Thanks, I’ve figured it out!
To dismiss this line of troubleshooting: do this only happen when creating issues with images? or it happens also with issues text-only?
This happened on starting the container, no issues were created yet, you can see I needed a minute to create a new issue after starting the container.
Just to confirm, the docker image worked as expected before migrating to k8s? or you had this error as well?
No, this error was new. I assume this was due to some version difference on my previous helm chart.
How did you add the “print_stack” statement? Did you clone the repo, change some files and build a new image? Or you’re adding manually inside a container?
I’ve added the statements by logging into the taiga-back container, then
apt update
apt install neovim
nvim <WHATEVER FILE I WAS DEBUGGING>
kill -HUP 1 #this restarts the workers with the new code
You guys should really consider officially supporting k8s, take the linked helm chart as a basis for your own. Now Taiga looks very nice in my cluster 
