Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Kubernetes manifests #91

Open
Hr46ph opened this issue Dec 6, 2024 · 6 comments
Open

Kubernetes manifests #91

Hr46ph opened this issue Dec 6, 2024 · 6 comments

Comments

@Hr46ph
Copy link

Hr46ph commented Dec 6, 2024

Hey, thanks for your work on this 😬 .

I created a bunch of manifests to deploy a statefulset using your image on my kubernetes cluster, mainly because I wanted to have more control over server configuration. I added a configMap with server settings json and I mount it using subMount for the file inside the pod.

Small changes: only query port udp is required these days, so left out the other port.

If you like I can share the files? I think I can do a fork and submit a merge request or something. Or I can post them here in code tags. Either way, let me know.

@jsknnr
Copy link
Owner

jsknnr commented Dec 7, 2024

I thought about using a stateful set when I built this out but decided for this use case it may be a little overkill since we only ever have the 1 pod. The config map is a great idea though and something I should have done, but I just leveraged the logic I already built for folks using things like compose and podman.

Feel free to open a PR and I will take a look.

@Hr46ph
Copy link
Author

Hr46ph commented Dec 7, 2024

Done!

I think manifests are the easiest way to deploy single pod deployments, nothing overkill about it. Its the docker-compose for Kubernetes, so to speak.

Anyway, have a look!

@jsknnr
Copy link
Owner

jsknnr commented Dec 7, 2024 via email

@jogalt
Copy link

jogalt commented Jan 9, 2025

Question for either of you, I'm attempting to install via helm and getting the following. @Hr46ph can you clarify how you defined the repo or annotated the index.yaml location?

helm install enshrouded steam-servers   --namespace steam-servers   --repo https://github.com/jsknnr/enshrouded-server   --values values.yaml --dry-run
Error: INSTALLATION FAILED: looks like "https://github.com/jsknnr/enshrouded-server" is not a valid chart repository or cannot be reached: failed to fetch https://github.com/jsknnr/enshrouded-server/index.yaml : 404 Not Found

@jsknnr
Copy link
Owner

jsknnr commented Jan 9, 2025 via email

@jogalt
Copy link

jogalt commented Jan 9, 2025

Closing the loop on this. I ended up having to clone the repo locally in rancher/helm gui vs doing a CLI pull. I'm able to stand up the server with no issues now so thanks for your work with packaging this.

As an aside, can you repackage the helm and generate an index.yaml file (for the k8s crowd) and push? This will allow installs without needing to clone the repo. Please and thank you.

helm package ./chart-directory
helm repo index --url https://github.com/jsknnr/enshrouded-server .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants