Error on deployment I ve been self hosting supertokens core

Question

Error on deployment I ve been self hosting supertokens core using supertokens postgresql v4 3 docker image on kubernetes with relative ease for a while now Today when I am trying to deploy it on a new cluster I am faced with this error Any idea what could be wrong I am not passing any port number just passing in the API KEYS and POSTGRESQL CONNECTION URI through environment variables ```What caused the crash com fasterxml jackson databind exc InvalidFormatException Cannot deserialize value of type `int` from String tcp 10 2 124 128 3567 not a valid `int` value at Source File line 194 column 7 through reference chain io supertokens config CoreConfig port ```

rp · Answer

hey < mayankgopronto>

rp · Answer

whats the `POSTGRESQL CONNECTION URI` that you are passing

mayankgopronto · Answer

`postgresql postgres welcome cloud sql proxy india default 5432 qadb`

rp · Answer

where is `tcp 10 2 124 128 3567` value coming

mayankgopronto · Answer

That must the private IP for that pod on kubernetes But I m not sure why that value is being passed in the connection string I am not sending that

rp · Answer

are you adding the PORT config

mayankgopronto · Answer

No not adding anything Just using the vanilla docker image

rp · Answer

thats weird Cause it s trying to read the port config and it s getting the string `tcp 10 2 124 128 3567` back

rp · Answer

maybe double check or configs

mayankgopronto · Answer

Ya its probably an infra issue How can I explicitly pass the port

mayankgopronto · Answer

Is this `port` referring to the postgresSQL port Or the port on which supertokens runs

rp · Answer

supertokens core port

mayankgopronto · Answer

Update So I fixed it by explicitly passing the port and the postgres connection params and ENV variables in the the helm chart like given here https github com supertokens supertokens docker postgresql blob master helm chart templates deployment yaml L43 instead of using the connection string in the kubernetes secrets But I have been running the same setup in my stage environment for a few weeks and everything was working fine Not sure what was the issue just one of those weird things I guess

rp · Answer

yeaaa strange