search

SickHub / ark-server-charts

A helm chart for an ARK Survival Evolved Cluster
GNU General Public License v3.0
13 stars 4 forks source link

Modifying a sever #21

Closed Dracozny closed 1 year ago

Dracozny commented 1 year ago

Perhaps just my ignorance with kubernetes but what would be the best approach to modifying a deployment. for instance if I wanted to add a map? I tried this: helm upgrade --namespace ark --values ~/ark-cluster/values.yaml arkcluster ark/ark-cluster but got a series of

spec is immutable after creation except resources.requests for bound claims

My workaround atm is to delete everything in the namespace and then delete the namespace and use the --install string instead.

Separate question, is there a way to make it not try to change the permissions on the folders/files? I have a remote store via fiber channel that is not set to have permissions changed. EDIT: I created a new file share that I can change permissions on, but it's still complaining about it not being able to chown. now I'm trying to figure out if that tidbit is a microk8 issue.

DrPsychick commented 1 year ago

There are certain specs in k8s objects that cannot be changed. To solve that, delete the object and re-run helm. Assuming you're still trying to get to a final setup.

The adjustment of permissions is required as the user starting the game server is 'steam': https://github.com/SickHub/arkserver/blob/master/run.sh#L14

But it could make sense to add an option to make that optional, i.e. the user must ensure the permissions are right.

Dracozny commented 1 year ago

Thanks for the reply. I will work on the user issue once I get my new (to me) hardware.

I can deal with deleting for now. But on the off chance that ARK releases a new map how would one go about adding that at a later date?

On Sat, Dec 10, 2022 at 3:28 AM DrPsychick @.***> wrote:

There are certain specs in k8s objects that cannot be changed. To solve that, delete the object and re-run helm. Assuming you're still trying to get to a final setup.

The adjustment of permissions is required as the user starting the game server is 'steam': https://github.com/SickHub/arkserver/blob/master/run.sh#L14

But it could make sense to add an option to make that optional, i.e. the user must ensure the permissions are right.

— Reply to this email directly, view it on GitHub https://github.com/DrPsychick/ark-server-charts/issues/21#issuecomment-1345243815, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA2PC6A6ICM2HDHZVJHV3R3WMRSOPANCNFSM6AAAAAASTZJVJU . You are receiving this because you authored the thread.Message ID: @.***>

DrPsychick commented 1 year ago

Adding a new map should result in an additional server, so that is easily done by extending the server list. Switching the map on an existing server would result in the same (add new, remove old).

Dracozny commented 1 year ago

right it would be an additional server. I guess I'm confused on the command structure. I'll tinker with a few ideas to hopefully understand better.

Dracozny commented 1 year ago

The adjustment of permissions is required as the user starting the game server is 'steam': https://github.com/SickHub/arkserver/blob/master/run.sh#L14

looking at that docker am I mistaken that the docker does not create that user/group? I see that it modifies it and it adds it to the sudo group in the main docker file but the creation of the user I'm not seeing.

Update: nvm. more searching shows it's during the install of steamcmd: https://github.com/thmhoag/steamcmd/blob/master/Dockerfile. so the issue on this bit was that I was not running the install with sudo.

DrPsychick commented 1 year ago

That's right. As you found, the Dockerfile is based on another Dockerfile while installs steamcmd and can serve as a base for other steam-based containers/games. https://github.com/SickHub/arkserver/blob/master/Dockerfile#L5 -> https://github.com/SickHub/steamcmd

DrPsychick commented 1 year ago

Closing this as there is no action to be taken as of now. Feel free to reopen or create a new issue.