The taiga-events image seems to be hardcoded with a reference to "taiga-events-rabbitmq" service, if you choose a helm release name
other than "taiga" like "myrelease", taiga-events will be trying to connect to a "myrelease-events-rabbitmq" service, which won't exist, ultimately causing the taiga-events pod from launching, causing ws:// or wss:// errors to be thrown in the console if the rest of taiga launches.
I was trying to release name with "ee-taiga"
$ kubectl -n taiga logs ee-taiga-events-0
Starting Taiga events
> taigaio-events@6.7.0 start:production
> NODE_ENV=production node ./src/index.js
{"message":"WS server is started","level":"info","service":"taiga-events","timestamp":"2023-10-09 04:09:33"}
{"message":"Liveness / Readiness server was started in http://localhost:3023/healthz","level":"info","service":"taiga-events","timestamp":"2023-10-09 04:09:33"}
{"message":"ws-connection-open: ae44e9b8-a029-475c-a301-1349fcd11a1b","level":"info","service":"taiga-events","timestamp":"2023-10-09 04:09:36"}
{"message":"auth: {\"cmd\":\"auth\",\"data\":{\"token\":\"eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJ0b2tlbl90eXBlIjoiYWNjZXNzIiwiZXhwIjoxNjk2ODkxNDE1LCJqdGkiOiI2NzE5ZDQzZGI4ZDg0MWNkYTFjYjg3ZDBkMjllZjhjMyIsInVzZXJfaWQiOjV9.s47hZgHGWGuO_x9CMWs-Fd6AxtHaAn4mDD-Cxc5yFpE\",\"sessionId\":\"d0477136de6a5c0844b31d6eb04c997606f2068d\"}}","level":"info","service":"taiga-events","timestamp":"2023-10-09 04:09:36"}
{"message":"subscribe: {\"cmd\":\"subscribe\",\"routing_key\":\"notifications\"}","level":"info","service":"taiga-events","timestamp":"2023-10-09 04:09:36"}
{"message":"subscribe: {\"cmd\":\"subscribe\",\"routing_key\":\"live_notifications.5\"}","level":"info","service":"taiga-events","timestamp":"2023-10-09 04:09:36"}
{"message":"subscribe: {\"cmd\":\"subscribe\",\"routing_key\":\"web_notifications.5\"}","level":"info","service":"taiga-events","timestamp":"2023-10-09 04:09:36"}
{"message":"Unhandled Rejection: \"Error: getaddrinfo ENOTFOUND taiga-events-rabbitmq\"","level":"error","service":"taiga-events","timestamp":"2023-10-09 04:09:36"}
The issue is the
{"message":"Unhandled Rejection: \"Error: getaddrinfo ENOTFOUND taiga-events-rabbitmq\"","level":"error","service":"taiga-events","timestamp":"2023-10-09 04:09:36"}
Workaround:
I wasn't able to figure out how to override this config, so i reinstalled my release w/ the standard name "taiga", and that got the events pod working again.
Just wanted to note this issue here, and solicit any suggestions for getting to that taiga-events config. I tried a few things but couldn't seem to find it.
The taiga-events image seems to be hardcoded with a reference to "taiga-events-rabbitmq" service, if you choose a helm release name other than "taiga" like "myrelease", taiga-events will be trying to connect to a "myrelease-events-rabbitmq" service, which won't exist, ultimately causing the taiga-events pod from launching, causing ws:// or wss:// errors to be thrown in the console if the rest of taiga launches.
I was trying to release name with "ee-taiga"
The issue is the {"message":"Unhandled Rejection: \"Error: getaddrinfo ENOTFOUND taiga-events-rabbitmq\"","level":"error","service":"taiga-events","timestamp":"2023-10-09 04:09:36"}
Workaround: I wasn't able to figure out how to override this config, so i reinstalled my release w/ the standard name "taiga", and that got the events pod working again.
Just wanted to note this issue here, and solicit any suggestions for getting to that taiga-events config. I tried a few things but couldn't seem to find it.