Browse Source

Release v1.4.0, compatibility with k8s 1.19+, no more fixed suffix for database

master
LecygneNoir 1 year ago
parent
commit
0b5049fec1
5 changed files with 25 additions and 13 deletions
  1. +13
    -2
      CHANGELOG.md
  2. +1
    -1
      Chart.yaml
  3. +5
    -5
      README.md
  4. +0
    -2
      templates/deployment.yaml
  5. +6
    -3
      templates/ingress.yaml

+ 13
- 2
CHANGELOG.md View File

@ -1,8 +1,19 @@
# v1.4.0
## Feature
- Upgrade Ingress template for k8s 1.19+ compatibility
- Remove fixed database suffix from deployment, please use production.yml to configure if default "_prod" is not sufficient
# v1.3.0
## Feature
- 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
# v1.2.1
## Fix
- Adjust initialDelaySecond for startupProbe to avoid waiting 5min even if the instance starts quickly
- Adjust startupProbe port to use 9000 instead of http
- Adjust startupProbe port to use 9000 instead of http
# v1.2.0
@ -24,7 +35,7 @@ Is you used it, configure your production.yml instead for better reliability.
# v1.1.0
## Features
## Features
Add a nginx sidecar to use the official Peertube optimisations for Nginx (Fix #2)

+ 1
- 1
Chart.yaml View File

@ -2,4 +2,4 @@ apiVersion: v1
appVersion: "v4.0.0-bullseye"
description: A Helm chart for Kubernetes
name: peertube
version: 1.2.1
version: 1.4.0

+ 5
- 5
README.md View File

@ -4,7 +4,7 @@ Federated (ActivityPub) video streaming platform using P2P (BitTorrent) directly
---
## Status : WIP
## Status : WIP bu workable
- [x] Run Peertube and Redis
- [x] Use pvc to persist data
@ -12,11 +12,11 @@ Federated (ActivityPub) video streaming platform using P2P (BitTorrent) directly
## Before deploying
Currently if you want use persistent volume you need to create persistent volume and persistent volume claim. You may use sample claims from `sample`:
Currently if you want use persistent volume you need to create persistent volume and persistent volume claim. You may use sample claims from `sample`:
- change the storageclass from `ChangeMeStorageClass` to your correct class
- apply the claim: `kubectl apply -f sample/claim.pvc-pt.yml`
You also need a postgresql server.
You also need a postgresql server.
If you know what you are doing and want to store postgres in Kubernetes, I suggest the excellent [stolon](https://github.com/helm/charts/tree/master/stable/stolon).
## Installing the chart
@ -40,5 +40,5 @@ See the sample/values.yml for example of values to use
## Source
Originated from https://github.com/MikaXII/helm-charts
Thanks!
Originated from https://github.com/MikaXII/helm-charts
Thanks!

+ 0
- 2
templates/deployment.yaml View File

@ -167,8 +167,6 @@ spec:
value: {{ .Values.environment.httpsEnabled | quote }}
- name: PEERTUBE_DB_HOSTNAME
value: {{ .Values.environment.dbHostname }}
- name: PEERTUBE_DB_SUFFIX
value: _prod
- name: PEERTUBE_DB_USERNAME
value: {{ .Values.environment.dbUser }}
- name: PEERTUBE_DB_PASSWORD

+ 6
- 3
templates/ingress.yaml View File

@ -1,7 +1,7 @@
{{- if .Values.ingress.enabled -}}
{{- $fullName := include "peertube.fullname" . -}}
{{- $ingressPath := .Values.ingress.path -}}
apiVersion: extensions/v1beta1
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: {{ $fullName }}
@ -31,8 +31,11 @@ spec:
http:
paths:
- path: {{ $ingressPath }}
pathType: Prefix
backend:
serviceName: {{ $fullName }}
servicePort: http
service:
name: {{ $fullName }}
port:
number: 9000
{{- end }}
{{- end }}

Loading…
Cancel
Save