dfd48b1626
1 Commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
e3mrah
|
dfd48b1626
|
fix(chart,api,controllers,ui): qa-loop iter-11 Fix #45 — three-cluster closeout (#1265)
Cluster-A (bp-guacamole PVC immutability):
- New pre-install/pre-upgrade Helm hook (Job + per-release SA/Role/
RoleBinding + cluster-scoped CR/CRB for PV cleanup) that detects
when an existing `guacamole-recordings` PVC is bound to a
storageClass different from `.Values.guacamole.recordings.storageClass`
and deletes the PVC + bound PV so the chart-side PVC manifest can
recreate cleanly. Closes the live bp-guacamole HelmRelease wedge on
omantel iter-11 (`PersistentVolumeClaim ... is invalid: spec:
Forbidden: spec is immutable after creation`).
- Operator escape hatch: `.Values.guacamole.recordings.allowMigration:
false` suppresses the hook for Sovereigns with long-lived recording
state.
- Render test extended (15 docs total, plus toggle assertion).
- bp-guacamole chart 0.1.8 → 0.1.9; bootstrap-kit slot pin bumped
in both _template and omantel.omani.works overlays.
Cluster-B (Application phase stuck on Provisioning):
- application-controller now observes the per-region downstream
HelmRelease.status.conditions[Ready] and rolls up
Application.status.phase: any region Ready=True → phase=Ready,
any Ready=False → phase=Degraded, no HR yet → phase=Provisioning.
- Periodic 30s re-list ticker (Run goroutine) so HR readiness flips
reach the Application even though the Application Watch doesn't
fire on sibling HR changes.
- status.lastReconciledAt populated on every reconcile pass for
TC-113.
- application-controller ClusterRole gains
helm.toolkit.fluxcd.io/helmreleases get/list/watch.
- 3 new unit tests (HR Ready=True → phase=Ready, HR Ready=False →
phase=Degraded with verbatim message, no-HR → phase=Provisioning).
Cluster-C (SPA AppDetail + k8s services namespace filter):
- GET /api/v1/sovereigns/{id}/applications/{name} returns full
Application detail (identity + spec + status). The SPA AppDetail
page now falls back to this endpoint when wizard store has no
descriptor for the requested componentId — the typical chroot
Sovereign case where Apps are installed via `kubectl apply` /
catalyst-api install endpoint, NOT via the wizard. Without the
fallback every chroot-installed Application surfaced "App not
found / The component qa-wp is not part of this deployment"
even though the underlying CR was Ready=True. Closes TC-068 /
TC-072 / TC-074 / TC-076 / TC-077 / TC-079 et al.
- GET /api/v1/sovereigns/{id}/k8s/{kind} accepts BOTH `?ns=`
(historic) AND `?namespace=` (kubectl/SPA-canonical). Without
the alias TC-262 / TC-263 returned every namespace's services
instead of qa-omantel-only. New test covers all 4 query
permutations.
Chart bumps:
- bp-catalyst-platform 1.4.116 → 1.4.117 (+ pin in
clusters/_template/bootstrap-kit/13-bp-catalyst-platform.yaml).
- bp-guacamole 0.1.8 → 0.1.9.
Refs: qa-loop iter-11 Fix #45 (Cluster-A + Cluster-B + Cluster-C);
post-merge image SHAs land via the catalyst-api / catalyst-controllers
build workflows + the bp-guacamole / bp-catalyst-platform release
workflows.
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|