Configuration for badhouseplants clusters
This repository has been archived on 2024-09-11. You can view files and clone it, but cannot push or open issues or pull requests.
Go to file
Nikolai Rodionov 0b23d53f10
chore(gitea): Upgrade the gitea chart version
The maintainer of the chart release a breaking chage, so this migration
was not easy. After the upgrade, I've copied all the data from the
previous installation, because the ReplicaSet provided was switched
from the StatefulSet to Deployment.

Issue: https://git.badhouseplants.net/badhouseplants/k8s-cluster-config/issues/86
2023-07-29 22:17:42 +02:00
badhouseplants chore(gitea): Upgrade the gitea chart version 2023-07-29 22:17:42 +02:00
bin refactor(istio-resource): Move all istio resource to helmfile 2023-04-17 11:10:48 +02:00
common migrate funkwhale to a dedicated database 2023-07-29 19:37:22 +02:00
etersoft Install drone-docker-runner to the etersoft cluster 2023-07-19 22:28:21 +02:00
manifests Uninstall mailu 2023-04-28 17:39:56 +02:00
.drone.yml update kubecontext setup 2023-07-20 18:19:44 +02:00
.sops.yaml Remove postgres secret from sops conf 2023-05-02 20:49:15 +02:00
environments.yaml update kubecontext setup 2023-07-20 18:19:44 +02:00
helmfile.yaml Install drone-docker-runner to the etersoft cluster 2023-07-19 22:28:21 +02:00
Makefile Create a ClusterRoleBinding to let drone operate in the cluster(#6) 2023-02-19 09:59:16 +00:00
README.md Install Prometheus 2023-05-28 09:42:02 +02:00
releases.yaml chore(gitea): Upgrade the gitea chart version 2023-07-29 22:17:42 +02:00
repositories.yaml install db-operator 2023-07-21 15:41:03 +02:00

Kubernetes configuration

Build Status

CRD hooks

I'm using hooks to install CRDs, that doesn't wotk with apply on the first time. If you've added a release with CRDs, that are installed by hooks, you need to run helmfile sync first, so CRDs are installed and then diff will work again, hence the apply also will.