Helm chart for deploying Peertube on kubernetes
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

66 lines
1.6 KiB

  1. # v1.4.0
  2. ## Feature
  3. - Upgrade Ingress template for k8s 1.19+ compatibility
  4. - Remove fixed database suffix from deployment, please use production.yml to configure if default "_prod" is not sufficient
  5. # v1.3.0
  6. ## Feature
  7. - Bump to peertube v4.0 by default. Warn if you are upgrading for 3.4, see release note for post maj script: https://github.com/Chocobozzz/PeerTube/releases/tag/v4.0.0
  8. # v1.2.1
  9. ## Fix
  10. - Adjust initialDelaySecond for startupProbe to avoid waiting 5min even if the instance starts quickly
  11. - Adjust startupProbe port to use 9000 instead of http
  12. # v1.2.0
  13. ## Features
  14. - Compatibility with helm 3 and k8s 1.16+
  15. - Now use StartupProbe to enable very long start when updating Peertube and running upgrade scripts
  16. # v1.1.2
  17. ## Fixes
  18. - Update compatibility to Peertube v2.3.0
  19. - Remove deprecated env variables for docker
  20. # v1.1.1
  21. Ensure compatibility with Peertube v2.2.0 by removing the PEERTUBE_TRUST_PROXY env variable that does not exist anymore.
  22. Is you used it, configure your production.yml instead for better reliability.
  23. # v1.1.0
  24. ## Features
  25. Add a nginx sidecar to use the official Peertube optimisations for Nginx (Fix #2)
  26. # v1.0.2
  27. ## Breaking changes
  28. The option initcontainer is now renamed chowncontainer as it fit better to its usage.
  29. ## Fixes
  30. - Fix issue #3 to avoid breaking Peertube upgrade by using 2 initContainers
  31. # v1.0.1
  32. Now use Peertube v2.1.0-buster as default
  33. # v1.0.0
  34. *Initial release*
  35. ##Features
  36. - Deploy Peertube in kubernetes
  37. - Deploy redis server to be used by Peertube
  38. - Allow to enable usual docker "chown" to speed up startup through InitContainer