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.

99 lines
2.6 KiB

  1. ---
  2. # Default values for peertube.
  3. # This is a YAML-formatted file.
  4. # Declare variables to be passed into your templates.
  5. replicaCount: 1
  6. image:
  7. repository: chocobozzz/peertube
  8. tag: v2.1.0-buster
  9. pullPolicy: IfNotPresent
  10. service:
  11. type: ClusterIP
  12. port: 9000
  13. ingress:
  14. enabled: true
  15. annotations:
  16. kubernetes.io/ingress.class: haproxy
  17. kubernetes.io/tls-acme: "true"
  18. certmanager.k8s.io/cluster-issuer: your-certmanager
  19. path: /
  20. hosts:
  21. - peertube.domain.tld
  22. tls:
  23. - secretName: crt-peertube.domain.tld
  24. hosts:
  25. - peertube.domain.tld
  26. # At start chowncontainer check every video files and chown it to peertube user.
  27. # If you have lots of videos, it may take age.
  28. # If you are sure your rights are ok, you may disable this container to speed up start.
  29. chowncontainer:
  30. enabled: true
  31. resources:
  32. # We usually recommend not to specify default resources and to leave this as a conscious
  33. # choice for the user. This also increases chances charts run on environments with little
  34. # resources, such as Minikube. If you do want to specify resources, uncomment the following
  35. # lines, adjust them as necessary, and remove the curly braces after 'resources:'.
  36. requests:
  37. cpu: 3
  38. memory: 6Gi
  39. nodeSelector: {}
  40. tolerations: []
  41. # NodeAffinity is useful if you want to specify some nodes for Peertube, eg nodes with high CPU for encoding for example
  42. #affinity:
  43. # nodeAffinity:
  44. # preferredDuringSchedulingIgnoredDuringExecution:
  45. # - weight: 1
  46. # preference:
  47. # matchExpressions:
  48. # - key: kubernetes.io/hostname
  49. # operator: In
  50. # values:
  51. # - yournodes.domain.tld
  52. # PVC are not handled by helm, you need to create both config and data volume before launching the helm
  53. persistence:
  54. data:
  55. enabled: true
  56. existingClaim: pvc-pt-prod
  57. config:
  58. enabled: true
  59. existingClaim: pvc-ptconfig-prod
  60. environment:
  61. hostname: peertube.domain.tld
  62. http: 443
  63. httpsEnabled: true
  64. dbHostname: your.postgresql.hostname
  65. dbUser: peertube
  66. dbPassword: postgres
  67. redisHostname: redis
  68. smtpUser: peertube@peertube.domain.tld
  69. smtpPassword: smtppassword
  70. smtpHostname: smtp.peertube.domain.tld
  71. smtpPort: 465
  72. smtpFrom: peertube@peertube.domain.tld
  73. smtpTls: true
  74. admin: peertube@peertube.domain.tld
  75. signup: false
  76. transcoding: true
  77. redis:
  78. usePassword: false
  79. password: peertube
  80. master:
  81. persistence:
  82. enabled: true
  83. path: /data
  84. # PVC are not handled by helm, you need to create redis volume before deploying helm
  85. persistence:
  86. enabled: true
  87. existingClaim: pvc-redis-prod