take the secrets out of the gitea values.yaml

This commit is contained in:
2023-11-01 09:36:56 -04:00
parent 3cfb3efedc
commit 3410213913
2 changed files with 82 additions and 1 deletions

View File

@@ -523,13 +523,22 @@ they decide to change things. This is the first chart (besides ingress-nginx) wh
we need to pay attention to the MetalLB annotation. This has been set in the values.yaml we need to pay attention to the MetalLB annotation. This has been set in the values.yaml
file. file.
First we need to create the gitea admin secret
```bash
kubectl create secret generic gitea-admin-secret \
--from-literal=username='' \
--from-literal=password='' \
--from-literal=email=''
```
```bash ```bash
helm repo add gitea-charts https://dl.gitea.io/charts/ helm repo add gitea-charts https://dl.gitea.io/charts/
helm repo update helm repo update
helm upgrade --install \ helm upgrade --install \
gitea \ gitea \
gitea-charts/gitea \ gitea-charts/gitea \
--values secrets/gitea-values.yaml \ --values gitea-values.yaml \
--namespace gitea \ --namespace gitea \
--create-namespace --create-namespace
``` ```

72
gitea-values.yaml Normal file
View File

@@ -0,0 +1,72 @@
ingress:
enabled: true
annotations:
cert-manager.io/cluster-issuer: letsencrypt
kubernetes.io/ingress.class: nginx
nginx.ingress.kubernetes.io/proxy-body-size: "0"
nginx.org/client-max-body-size: "0"
hosts:
- host: gitea.reeseapps.com
paths:
- path: /
pathType: Prefix
tls:
- hosts:
- gitea.reeseapps.com
secretName: gitea-tls-cert
persistence:
enabled: true
create: false
storageClass: zfs-iscsi-enc0
claimName: data-gitea-0
annotations:
"helm.sh/resource-policy": keep
global:
storageClass: zfs-iscsi-enc1
postgresql:
enabled: true
primary:
persistence:
enabled: true
storageClass: zfs-iscsi-enc1
annotations:
"helm.sh/resource-policy": keep
postgresql-ha:
enabled: false
gitea:
admin:
existingSecret: gitea-admin-secret
config:
service:
DISABLE_REGISTRATION: true
service:
ssh:
port: 2222
type: LoadBalancer
externalTrafficPolicy: Cluster
annotations:
metallb.universe.tf/address-pool: "production"
metallb.universe.tf/allow-shared-ip: "production"
redis-cluster:
enabled: true
deployment:
tolerations:
- key: "node.kubernetes.io/unreachable"
operator: "Exists"
effect: "NoExecute"
tolerationSeconds: 1
- key: "node.kubernetes.io/not-ready"
operator: "Exists"
effect: "NoExecute"
tolerationSeconds: 1
strategy:
type: Recreate