50ceb6d98d
FIX(argocd): falco cpu requests in argocd
...
- application
- Falco: 100m → 30m
- Falcosidekick Web UI: 50m → 30m
The previous commit only updated helm-values/falco.yaml which wasn't
being used. The ArgoCD Application uses inline helm values.
2026-01-04 23:41:39 +09:00
27d26cdfb3
CHORE(falco): ignore volumeClaimTemplates status
...
- in falco StatefulSet
2026-01-04 23:41:39 +09:00
8a398a3bdc
REFACTOR(falco): use cpu: null
...
- to delete Helm chart default CPU limit...
Following Helm best practice to override default values with null.
2026-01-04 23:41:39 +09:00
6e1304f703
FIX(falco): re-enable auto-sync
...
- for falco and use Helm chart defaults
Let Helm chart apply default CPU limits like other apps.
2026-01-04 23:41:39 +09:00
d6b9fe6a01
CHORE(falco): disable auto-sync for falco
...
- to allow manual CPU limit r...
Will manually patch DaemonSet to remove CPU limits after this is
applied.
2026-01-04 23:41:39 +09:00
85ef6e8c9f
CHORE(falco): set Falco CPU limit to empty string
...
- Override Helm default CPU limit
- Prevent throttling
2026-01-04 23:41:39 +09:00
10211f35bc
REFACTOR(falco): remove invalid empty string CPU
...
- limit from falco
Kubernetes rejects cpu: "" as invalid quantity format. Will allow
DaemonSet
to be created with default CPU limit, then manually patch and disable
auto-sync.
2026-01-04 23:41:39 +09:00
fa98684528
CHORE(falco): set Falco CPU limit to empty string
...
- Override Helm default CPU limit
- Prevent throttling
2026-01-04 23:41:39 +09:00
1408000e4c
REFACTOR(falco): remove cpu limits entirely
...
- from vault and falco
- Remove cpu line from limits section (not just set to null)
- Prevents Helm charts from applying default CPU limit values
- Eliminates CPU throttling for infrastructure components
2026-01-04 23:41:39 +09:00
9d8a0554c8
FIX(falco): set Falco CPU limit to null
...
- Explicitly set CPU limit to null
- Prevent throttling
2026-01-04 23:41:39 +09:00
5c0e5364b9
REFACTOR(resources): remove cpu limits
...
- from infrastructure components
- velero-ui: Remove 200m CPU limit
- metallb controller: Remove 100m CPU limit
- metallb speaker: Remove 100m CPU limit (300m total across 3 nodes)
- falco: Remove 1000m CPU limit (3000m total across 3 nodes)
Total CPU limits removed: ~3600m
This eliminates CPU throttling and reduces CPU limits overcommit from
131% to 0%.
2026-01-04 23:41:39 +09:00
ac5fde6ba4
FIX(repo): simplify ignoreDiff for all StatefulSets
...
- Simplify ignoreDifferences configuration
- Reduce complexity
2026-01-04 23:41:39 +09:00
70eb551871
FIX(falco): disable selfHeal for Falco
...
- Prevent StatefulSet drift issues
- Disable automatic healing
2026-01-04 23:41:39 +09:00
3f18a3cdf8
FEAT(repo): enhance syncPolicy and ignoreDiff for StatefulSet
...
- Add enhanced sync policy
- Configure ignoreDifferences for StatefulSet
2026-01-04 23:41:39 +09:00
c2b9175b8b
FIX(storage): improve ignoreDiff for StatefulSet PVC retention
...
- Improve ignoreDifferences configuration
- Handle PVC retention policy
2026-01-04 23:41:39 +09:00
18dac6b77f
FIX(falco): change Falco driver to modern_ebpf
...
- Use modern_ebpf driver for kernel 6.14 compatibility
- Fix kernel module issues
2026-01-04 23:41:39 +09:00
10308d48d0
FEAT(velero): Add Velero, Falco,
...
- and CNPG infrastructure components
Add three critical infrastructure components via GitOps:
- Velero: Backup and disaster recovery solution
- Configured with Minio S3 backend
- Daily full cluster backups (30-day retention)
- Hourly backups for critical namespaces (7-day retention)
- Credentials managed via External Secrets from Vault
- Falco: Runtime security monitoring
- eBPF-based threat detection
- Custom rules for container security
- Falcosidekick for alert forwarding
- Prometheus metrics enabled
- CNPG (CloudNativePG): PostgreSQL operator
- Kubernetes-native PostgreSQL management
- Automated failover and backups
- Will replace Bitnami PostgreSQL
All components follow existing GitOps patterns:
- Helm charts deployed via ArgoCD
- Values managed in Git
- Automated sync with selfHeal enabled
2026-01-04 23:41:39 +09:00
