Kubernetes | Palworld infinite Waiting for user info about palworld-server-docker

[alex4108]

Take a look at manifests here if you want inspiration of how I'm running this. Yes you need LoadBalancer type to get an external IP so others can connect.

https://github.com/alex4108/palworld-on-kubernetes

[thijsvanloef]

Hi @Enorshionari, thanks for taking the time to write an issue, at the moment there is an open pull request aimed to get my palworld container working for Kubernetes. You should check it out, no doubt your input would be helpful :)
#65

[Enorshionari]

I have no idea why, but after ~2 hours in this state game successfully pulled from steam and started server.

Connecting anonymously to Steam Public...OK
Waiting for client config...OK
Waiting for user info...
steamcmd has been disconnected from steam with result 3 (No Connection)
FAILED (Timed out)
OK
>>> Starting the gameserver
Checking if config exists
Setting rcon-enabled to true
Setting public ip to %private-ip%
Setting public port to 8211
Setting server name to kubernetes-server-1
Setting server description to Palworld-Test-Server running in kubernetes by https://t.me/SevenSilentStar
sed: -e expression #1, char 101: unknown option to `s'
Setting server password to 12345
Setting server admin password to 12345
Setting max-players to 32
[S_API] SteamAPI_Init(): Loaded local 'steamclient.so' OK.
Shutdown handler: initalize.
- Existing per-process limit (soft=1048576, hard=1048576) is enough for us (need only 1048576)
Increasing per-process limit of core file size to infinity.
- Existing per-process limit (soft=18446744073709551615, hard=18446744073709551615) is enough for us (need only 18446744073709551615)
CAppInfoCacheReadFromDiskThread took 0 milliseconds to initialize
Setting breakpad minidump AppID = 2394010
[S_API FAIL] Tried to access Steam interface SteamUser021 before SteamAPI_Init succeeded.
[S_API FAIL] Tried to access Steam interface SteamFriends017 before SteamAPI_Init succeeded.
[S_API FAIL] Tried to access Steam interface STEAMAPPS_INTERFACE_VERSION008 before SteamAPI_Init succeeded.
[S_API FAIL] Tried to access Steam interface SteamNetworkingUtils004 before SteamAPI_Init succeeded.

Also, can someone clarify, do we need to use loadbalancer with direct access to pod via 8211 UDP and 25575 TCP?

[thijsvanloef]

k8s support has just been merged #65, closing the issue.