feat: add a helm chart to deploy PMS Kubernetes #82
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.
closes: https://github.com/plexinc/operations/issues/2886
Adds a new method to deploy a PMS container to a Kubernetes cluster.
This chart will deploy a
StatefulSet
with a single instance of of PMS.Data volumes can be mounted by creating
PersistentVolume
s or by using therclone
sidecars to be able to easily mount drives from arbitrary locations that may not have Kubernetes drivers.By default this chart will create a PMS service internal to the cluster that is published on the standard PMS port.
However, this will now allow direct external connections to PMS.
A builtin ingress controller has been provided that will allow PMS to be accessed over the standard HTTP(s) ports, this will require manually reconfiguring the PMS instance to advertise using this url.