Docker/planka
Docker/planka
1
0
Fork 0
mirror of https://github.com/plankanban/planka.git synced 2025-08-05 13:35:27 +02:00
Code Issues Releases Activity

feat: Version 2

Browse source 
Closes #627, closes #1047
This commit is contained in:
Maksim Eltyshev 2025-05-10 02:09:06 +02:00
parent ad7fb51cfa
commit 2ee1166747
1557 changed files with 76832 additions and 47042 deletions
Download patch file Download diff file Expand all files Collapse all files

6
charts/planka/Chart.lock
View file

@ -1,6 +1,6 @@
dependencies:
- name: postgresql
repository: https://charts.bitnami.com/bitnami
version: 12.5.1
digest: sha256:01dfb2d07ab6800b4a5a6c81f20f3377a758124b2b96b891d0cd6b4f64cf783b
generated: "2023-05-15T00:54:48.1308917+01:00"
version: 16.6.6
digest: sha256:b52a26ab3fb7ec9415c7e4ab2e8676d964830d71708bffbf975e10b31bbb2cb1
generated: "2025-04-25T17:38:31.821861+02:00"

8
charts/planka/Chart.yaml
View file

@ -1,6 +1,6 @@
apiVersion: v2
name: planka
description: A Helm chart to deploy Planka and it's dependencies.
description: A Helm chart to deploy PLANKA and it's dependencies.
# A chart can be either an 'application' or a 'library' chart.
#
@ -15,17 +15,17 @@ type: application
# This is the chart version. This version number should be incremented each time you make changes
# to the chart and its templates, including the app version.
# Versions are expected to follow Semantic Versioning (https://semver.org/)
version: 0.2.25
version: 1.0.0
# This is the version number of the application being deployed. This version number should be
# incremented each time you make changes to the application. Versions are not expected to
# follow Semantic Versioning. They should reflect the version the application is using.
# It is recommended to use it with quotes.
appVersion: "1.26.2"
appVersion: "2.0.0-rc.2"
dependencies:
- alias: postgresql
condition: postgresql.enabled
name: postgresql
repository: &bitnami-repo https://charts.bitnami.com/bitnami
version: 12.5.1
version: 16.6.6

16
charts/planka/README.md
View file

@ -1,8 +1,8 @@
# Planka Helm Chart
# PLANKA Helm Chart
[Planka](https://github.com/plankanban/planka) is an OSS alternative to Trello that you can host yourself, and this is a Helm Chart to make it easier to deploy to K8s.
This Helm Chart simplifies the deployment of [PLANKA](https://github.com/plankanban/planka) on Kubernetes.
Shoutout to [this issue](https://github.com/plankanban/planka/issues/192) who have been asking for this Helm Chart.
Shoutout to [this issue](https://github.com/plankanban/planka/issues/192) for requesting a Helm Chart!
## Issues
@ -32,9 +32,9 @@ helm install planka . --set secretkey=$SECRETKEY \
--set admin_username="demo"
```
> **NOTE:** The command `openssl rand -hex 64` is needed to create a random hexadecimal key for planka. On Windows you can use Git Bash to run that command.
> **Note:** The command `openssl rand -hex 64` is needed to create a random hexadecimal key for planka. On Windows you can use Git Bash to run that command.
To access Planka you can port forward using the following command:
To access PLANKA you can port forward using the following command:
```bash
kubectl port-forward $POD_NAME 3000:1337
@ -42,7 +42,7 @@ kubectl port-forward $POD_NAME 3000:1337
### Accessing Externally
To access Planka externally you can use the following configuration
To access PLANKA externally you can use the following configuration
```bash
# HTTP only
@ -70,7 +70,7 @@ or create a values.yaml file like:
```yaml
secretkey: "<InsertSecretKey>"
# The admin section needs to be present for new instances of Planka, after the first start you can remove the lines starting with admin_. If you want the admin user to be unchangeable admin_email: has to stay
# The admin section needs to be present for new instances of PLANKA, after the first start you can remove the lines starting with admin_. If you want the admin user to be unchangeable admin_email: has to stay
# After changing the config you have to run ```helm upgrade planka . -f values.yaml```
# Admin user
@ -102,7 +102,7 @@ helm install planka . -f values.yaml
### Things to consider if production hosting
If you want to host Planka for more than just playing around with, you might want to do the following things:
If you want to host PLANKA for more than just playing around with, you might want to do the following things:
- Create a `values.yaml` with your config, as this will make applying upgrades much easier in the future.
- Create your `secretkey` once and store it either in a secure vault, or in your `values.yaml` file so it will be the same for upgrading in the future.

7
charts/planka/templates/deployment.yaml
View file

@ -50,11 +50,14 @@ spec:
path: /
port: http
volumeMounts:
- mountPath: /app/public/favicons
subPath: favicons
name: planka
- mountPath: /app/public/user-avatars
subPath: user-avatars
name: planka
- mountPath: /app/public/project-background-images
subPath: project-background-images
- mountPath: /app/public/background-images
subPath: background-images
name: planka
- mountPath: /app/private/attachments
subPath: attachments

6
charts/planka/values.yaml
View file

@ -27,7 +27,7 @@ existingSecretkeySecret: ""
## NOTE: When it's set, the `admin_username` and `admin_password` parameters are ignored
existingAdminCredsSecret: ""
# Base url for Planka. Will override `ingress.hosts[0].host`
# Base url for PLANKA. Will override `ingress.hosts[0].host`
# Defaults to `http://localhost:3000` if ingress is disabled.
baseUrl: ""
@ -57,7 +57,7 @@ service:
annotations: {}
type: ClusterIP
port: 1337
## @param service.containerPort Planka HTTP container port
## @param service.containerPort PLANKA HTTP container port
## If empty will default to 1337
##
containerPort: 1337
@ -176,7 +176,7 @@ oidc:
## @param oidc.scopes A list of scopes required for OIDC client.
## If empty will default to `openid`, `profile` and `email`
## NOTE: Planka needs the email and name claims
## NOTE: PLANKA needs the email and name claims
##
scopes: []