The Strela Init Container destroys configs #3
Description
The issue
The strela init container does nothing without a volume attached to the primary container. If you now mount that volume, you immediately break your image, because everything is gone. You would need to mount the volumeMount with a subPath in order for your images content to actually exist at all.
But now there is a new problem. If you change ANY CONFIG in the image, you are out of luck. Strela will just overwrite it. You don't have any options. You need to just live with the fact, that you cannot expect the velocity secret or max players to be set how you like it.
The fix
I'm not Kubernetes expert. But as far as I'm concerned, there is no fix. The init container will probably never be able to read files from the image of the primary container.
A custom image for proxies, servers etc. would be a solution, but in my eyes far from a perfect one. However, it would certainly be better than what we currently have. Since these fields would need to be passed as env variables anyway, I could adjust my own images and it would be fine.