From 3559ef95bf78fcd401a18e13ec7785cd1fb181ef Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Florian=20G=C3=A4nsejunge?= Date: Wed, 30 Sep 2026 13:23:01 +0000 Subject: [PATCH] Updated readme --- README.md | 12 +----------- 1 file changed, 1 insertion(+), 11 deletions(-) diff --git a/README.md b/README.md index bced892..4b46e77 100644 --- a/README.md +++ b/README.md @@ -1,6 +1,6 @@ # ops-deployment -This repository contains declarative Kubernetes configurations (deployments, services, persistent volumes) for all application services. Changes are automatically synchronized to the cluster by Flux. +This repository contains declarative Kubernetes configurations (deployments, services, persistent volumes) for all application services. ## Structure @@ -9,26 +9,16 @@ Each service directory contains: - `service.yaml` - Service exposure (ClusterIP, NodePort) - Additional resources as needed (PVCs, ConfigMaps, etc.) -## Workflow - -1. **CI/CD Pipeline**: Build process generates new container image -2. **Automatic Update**: Pipeline commits updated image tag to this repository -3. **Flux Synchronization**: Flux detects changes and applies to cluster -4. **Rolling Deployment**: Kubernetes performs rolling update ## Secrets Management Secrets are managed directly in Kubernetes using `kubectl` or sealed-secrets: -- Never committed to this repository - Mounted as volumes at `/etc/secrets` in containers - Referenced via `secretName` in deployment manifests ## Persistent Storage Services requiring data persistence (MySQL, RabbitMQ) use PersistentVolumeClaims: -- Storage classes define volume provisioning -- Data survives pod restarts and redeployments -- Backups handled separately ## Example Service