Repository navigation
Added some docs to run on Kubernetes - #304
Merged
Merged
Conversation
|
related: #271 Some of your deployment manifests are similar to what I tweaked. The other things on the list:
I was able to get the web container mounted w/ a read only file system after poking a few holes: volumes:
- name: media
persistentVolumeClaim:
claimName: opengym-media
# readOnlyRootFilesystem makes the image read-only, but these emptyDir mounts provide writable paths for temporary files.
# Their contents are discarded with the Pod; persistent media stays on the PVC above.
# The media init container clones the dataset into /tmp before copying it to the PVC.
- name: media-tmp
emptyDir: {}
# nginx copies the upstream template here to enable IPv6 DNS resolution.
- name: nginx-tmp
emptyDir: {}
# The nginx entrypoint renders its configuration into this writable directory.
- name: nginx-config
emptyDir: {}
# nginx needs writable request buffers and temporary cache files.
- name: nginx-cache
emptyDir: {}
# nginx writes its PID and runtime files here.
- name: nginx-run
emptyDir: {} |
DuarteSantos8
added a commit
that referenced
this pull request
Sep 28, 2026
…ng guide, the gateway may read the certificate, and the manifests say what to set
DuarteSantos8
added a commit
that referenced
this pull request
Sep 28, 2026
…in the images to a release and the media download to a git version, and the guide says why TRUST_PROXY stays off behind a gateway
DuarteSantos8
added a commit
that referenced
this pull request
Sep 28, 2026
Owner
|
Thanks @chriscowley, the Kubernetes manifests and guide are in. On top: the manifests create their namespace, pin the images to a release and the media download to a git version, the guide is linked from the self-hosting guide, and it explains why @kquinsland01, thanks for the notes. Health/ready probes and the read-only-filesystem tweaks would be welcome as a follow-up PR. Released in v1.3.9: https://github.com/DuarteSantos8/openGym/releases/tag/v1.3.9 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I deployed my instance on Kubernetes (documented here), but decided to feed what I did back to the community.
This is a very basic set of manifests to deploy on a cluster similar to my own:
There are other ways to do this that would be more scalable, such as putting the API and frontend in separate deployments, but this will work for most people.
TODO: put this into a Helm chart, but that would be another MR