fix(platform): explicit keda.crds.install + keda-add-ons-http.crds.install — auto-bootstrap CRDs on every server
Without this, KEDA crashloops on fresh servers because the parent-subchart values merge resolves crds.install=false despite the subcharts default of true. Manual remediation was kubectl apply --server-side -f keda-crds.yaml. Codified now so any client onboarding works first try. Repro: havari-server03 onboarding 2026-05-10 stalled at OutOfSync until manual CRD apply.
This commit is contained in:
@@ -23,8 +23,8 @@ description: |
|
||||
Git).
|
||||
|
||||
type: application
|
||||
version: 0.7.4
|
||||
appVersion: "0.7.4"
|
||||
version: 0.7.5
|
||||
appVersion: "0.7.5"
|
||||
|
||||
# All 6 subcharts now resolve from registry.odoosky.cloud (mirrored
|
||||
# 2026-05-08, KEDA stack added 2026-05-09). Mirror-first discipline
|
||||
|
||||
Reference in New Issue
Block a user