Streama is a self-hosted streaming media server which provides a modern UI, authentication and many functionalities such as subtitles and trailers just like Netflix.
This chart installs the full Streama application on a Kubernetes cluster using the Helm package manager.
It includes the Bitnami MySQL chart which is required to bootstrap a MySQL deployment for the database requirements of the Streama application.
This chart expects to be managed as a standard Helm chart. All the commands from the Helm CLI apply.
See the official Helm CLI documentation for commands description.
See Customizing the Chart Before Installing. To see all configurable options with detailed comments:
helm show values .
Values definition are also available in the values.schema.json file.
The mysql parameters maps to MySQL sub-chart parameters. For more information please refer to the MySQL parameters documentation.
If you wish to use an external database instead of the one that is automatically install in the sub-chart, set the mysql.enabled value to false and link Streama with your database by defining the externalDatabase value.
The Streama application needs persistent storage to store media data. You can create a Persistent Volume Claim with this chart or use an already existing PVC by configuring the persistence value.
Although it is possible to disable persistence by setting the persistence.enabled value to false, it is not recommended to do this in production.
This chart provides support for ingress resources. You may enable it by setting the ingress.enabled value to true. In that case you must set the ingress.host value and make a corresponding DNS record point to the Ingress load balancing IP.
It is recommended to use nginx-ingress as Ingress Controller to serve your Streama application given that it provides cookie-session-affinity which is essential to make Streama work with several replicas.