The Docker-based CI/CD approach is the industry standard but requires: - Proper container registry (GHCR, Docker Hub) with HTTPS - Or complex local registry setup with containerd HTTP configuration The init container approach works reliably for now. To enable auto-deploy: 1. Flux detects git changes in 30s (via webhook) 2. Kustomization applies new config 3. Manually run: kubectl rollout restart deployment/storefront -n manoonoils For true auto-deploy, consider: - Setting up GHCR with proper auth - Using GitHub Actions to build/push images - Using Flux ImageUpdateAutomation Or simpler: A post-deploy webhook that triggers rollout restart.
7 lines
136 B
YAML
7 lines
136 B
YAML
apiVersion: kustomize.config.k8s.io/v1beta1
|
|
kind: Kustomization
|
|
resources:
|
|
- deployment-nodejs.yaml
|
|
- service.yaml
|
|
- ingress.yaml
|