jovies

Files

Mayne0213 37a7dbd561 CHORE(deploy): use argocd for kaniko

Infrastructure as Code:
- Add Kaniko namespace and RBAC manifests
- Create ArgoCD Application for Kaniko infrastructure
- Kustomize configuration for Kaniko resources

Workflow improvements:
- Remove kubeconfig dependency
- Use in-cluster ServiceAccount (runner runs in K8s)
- Remove all sudo commands
- Simplify Kubernetes access

GitOps workflow:
1. Push manifests to Git
2. ArgoCD auto-syncs infrastructure
3. Gitea runner uses ServiceAccount permissions
4. Kaniko builds run in kaniko-builds namespace

Benefits:
- True GitOps approach
- No secrets management needed
- Declarative infrastructure
- ArgoCD handles reconciliation
- Audit trail in Git

2025-12-28 17:36:10 +09:00

application-dev.yaml

REFACTOR(deploy): move argocd manifests

2025-12-17 18:27:23 +09:00

application-kaniko-infra.yaml

CHORE(deploy): use argocd for kaniko

2025-12-28 17:36:10 +09:00

application-prod.yaml

FEAT(deploy): add prod argocd app

2025-12-17 20:28:07 +09:00

application.yaml

CHORE(deploy): update argocd path