473de53cff
Some checks failed
Build and Push to Harbor / build-and-push (push) Has been cancelled
- Add Tekton pipeline and triggers for automated builds on git push - Add Flux ImageRepository to track Harbor registry images - Add Flux ImagePolicy for semantic versioning strategy - Add Flux ImageUpdateAutomation to auto-update HelmRelease - Update HelmRelease with image automation marker - Add comprehensive CI/CD pipeline setup documentation This enables automatic build and deployment when pushing to Gitea: 1. Gitea webhook triggers Tekton pipeline 2. Kaniko builds and pushes image to Harbor 3. Flux detects new image and updates deployment 4. Application automatically deploys to cluster 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
22 lines
489 B
YAML
22 lines
489 B
YAML
apiVersion: helm.toolkit.fluxcd.io/v2
|
|
kind: HelmRelease
|
|
metadata:
|
|
name: neon-vortex
|
|
namespace: default
|
|
spec:
|
|
interval: 5m
|
|
chart:
|
|
spec:
|
|
chart: ./neon-vortex-chart
|
|
sourceRef:
|
|
kind: GitRepository
|
|
name: neon-vortex
|
|
namespace: flux-system
|
|
interval: 1m
|
|
values:
|
|
image:
|
|
registry: images.caffeinetux.com
|
|
repository: apps/neon-vortex
|
|
tag: latest # {"$imagepolicy": "flux-system:neon-vortex:tag"}
|
|
pullPolicy: Always
|