Files
bakery-ia/infrastructure
Bakery Admin dac79a4ad6 Temp: Use folder-based image names to match existing registry [skip ci]
This is a temporary workaround to test Flux reconciliation.
The registry currently has images stored with folder names (auth, tenant, etc.)
instead of service names (auth-service, tenant-service, etc.).

The permanent fix in task-kaniko-build.yaml will push with correct names
on the next full pipeline run.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2026-01-23 15:44:28 +01:00
..
2026-01-22 16:24:03 +01:00
2026-01-19 13:57:50 +01:00
2026-01-19 15:15:04 +01:00
2026-01-19 13:57:50 +01:00
2026-01-19 11:55:17 +01:00

Bakery-IA Infrastructure

This directory contains all infrastructure-as-code for the Bakery-IA project, organized according to best practices for maintainability and scalability.

Directory Structure

infrastructure/
├── environments/                # Environment-specific configurations
│   ├── dev/                   # Development environment
│   │   ├── k8s-manifests/     # Kubernetes manifests for dev
│   │   └── values/            # Environment-specific values
│   ├── staging/               # Staging environment
│   │   ├── k8s-manifests/
│   │   └── values/
│   └── prod/                  # Production environment
│       ├── k8s-manifests/
│       ├── terraform/         # Production-specific IaC
│       └── values/
├── platform/                  # Platform-level infrastructure
│   ├── cluster/               # Cluster configuration (EKS, Kind)
│   ├── networking/            # Network configuration
│   ├── security/              # Security policies and TLS
│   └── storage/               # Storage configuration
├── services/                  # Application services
│   ├── databases/             # Database configurations
│   ├── api-gateway/           # API gateway configuration
│   └── microservices/         # Individual microservice configs
├── monitoring/                # Observability stack
│   └── signoz/                # SigNoz configuration
├── cicd/                      # CI/CD pipeline components
├── security/                  # Security configurations
├── scripts/                   # Automation scripts
└── docs/                      # Infrastructure documentation

Environments

Each environment (dev, staging, prod) has its own configuration with appropriate isolation and security settings.

Services

Services are organized by business domain with clear separation between databases, microservices, and infrastructure components.

Getting Started

  1. Local Development: Use tilt up to start the development environment
  2. Deployment: Use skaffold run to deploy to your target environment
  3. CI/CD: Tekton pipelines manage automated deployments

Security

Security configurations are centralized in the security/ directory with:

  • TLS certificates and rotation scripts
  • Network policies
  • RBAC configurations
  • Compliance checks