Google Cloud deployment - crashing on bad port about charts HOT 5 CLOSED

This problem is a Kubernetes thing. When you deploy the whole thing with the name soketi, you also get a service with the name soketi. This creates in the namespace the environment variable SOKETI_PORT that is injected into the pod. Since soketi is using this env as port env, it will be overwritten with the generated env from the service, that leads to the error.

from charts.

There is an answer is posted here: soketi/soketi#766
In that case, you edit values.yml if using the helm chart. Pick any nameOverride value which is not exactly soketi.

If you are not using Helm, you can also edit the app name and the prefix for the other values, but it is only required for you to change the service names which are named "soketi" or "soketi_cluster".

from charts.

Ended up getting this to work with a little different setup for GKE, but it is working.

from charts.

Hi @mfreeman451 can you share your solution?

from charts.

Ah this bugged me as well...

from charts.