Updated readme
This commit is contained in:
1 parent
7674a9c64b
commit
3559ef95bf
1 file changed
+1
-11
@@ -1,6 +1,6 @@
|
|||||||
# ops-deployment
|
# 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
|
## Structure
|
||||||
|
|
||||||
@@ -9,26 +9,16 @@ Each service directory contains:
|
|||||||
- `service.yaml` - Service exposure (ClusterIP, NodePort)
|
- `service.yaml` - Service exposure (ClusterIP, NodePort)
|
||||||
- Additional resources as needed (PVCs, ConfigMaps, etc.)
|
- 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 Management
|
||||||
|
|
||||||
Secrets are managed directly in Kubernetes using `kubectl` or sealed-secrets:
|
Secrets are managed directly in Kubernetes using `kubectl` or sealed-secrets:
|
||||||
- Never committed to this repository
|
|
||||||
- Mounted as volumes at `/etc/secrets` in containers
|
- Mounted as volumes at `/etc/secrets` in containers
|
||||||
- Referenced via `secretName` in deployment manifests
|
- Referenced via `secretName` in deployment manifests
|
||||||
|
|
||||||
## Persistent Storage
|
## Persistent Storage
|
||||||
|
|
||||||
Services requiring data persistence (MySQL, RabbitMQ) use PersistentVolumeClaims:
|
Services requiring data persistence (MySQL, RabbitMQ) use PersistentVolumeClaims:
|
||||||
- Storage classes define volume provisioning
|
|
||||||
- Data survives pod restarts and redeployments
|
|
||||||
- Backups handled separately
|
|
||||||
|
|
||||||
## Example Service
|
## Example Service
|
||||||
|
|
||||||
|
|||||||
Reference in new issue
Block a user