ADR-0169: Perses and Infisical OSS removed: dashboards in the Navin Manager and the portal, secrets in OpenBao or the client vault
Context
ADR-0109 chose Perses (Apache-2.0) instead of Grafana (AGPL-3.0) as dashboard server: an Argo CD application with its chart repository and k8s-sidecar, a service of the compose stack, a service of the Navin Manager catalog, eleven platform dashboards, ClickHouse and OpenSearch data sources, links in the Manager telemetry, an operator console of the portal and pack dashboards checked by percli. Infisical OSS (MIT) was offered as a secrets store next to OpenBao: a service of the Manager catalog, a console, a Hub entry and a component of the inventory. On 2026-11-01 the user decided to remove them from every list: the platform does not need them.
Decision
- Perses is removed from the whole product: Navin Manager catalog and templates, Kubernetes and Argo CD deployment (with k8s-sidecar, used by it only), compose stack, Cilium policies, secrets of its data sources, dashboards of
deploy/observability, the percli tool, links of the Manager telemetry, thepersesconsole of the control plane and the portal (EAI_PERSES_URL), the component inventory. - Dashboards are in the Navin products: machines and services in the Navin Manager (monitoring tab with its history in the database, host metrics, telemetry export to ClickHouse); agents, LLM gateway, FinOps, SLO and security in the screens of the portal. Logs in OpenSearch Dashboards, traces in Jaeger and Opik, metrics and alerts in Prometheus and Alertmanager: the alert and recording rules do not change. A Grafana already run by the client can still be linked as a console (
EAI_GRAFANA_URL), never deployed by the platform (AGPL, ADR-0101). - Marketplace packs no longer ship dashboards: the packs SDK refuses the
observability/dashboardsfolder, the marketplace archive refuses it too and the gates no longer use percli. The alert rules (promtool) and the SLO of the packs stay. - Infisical OSS is removed: service, templates and console of the Navin Manager, Hub entry, component of the inventory and documentation. Secrets stay in OpenBao (ADR-0112) or in the client vault, through External Secrets.
- ADR-0109 is superseded by this decision and stays as history; the original kit is not changed.
Alternatives considered
- Keep Perses as an optional service: eleven dashboards, a checking tool and data source secrets to maintain for views the Navin Manager and the portal already give.
- Keep Infisical OSS as an option: a second secrets store to secure, audit and update, duplicating OpenBao and the client vault.
Consequences
One server less to deploy, expose, secure and update, and a single secrets store shipped. The pack format changes: a pack that contains observability/dashboards is refused; the shipped packs and the templates are updated. A client who wants their own Grafana dashboards keeps their Grafana and links it to the portal.
Evidence
services/control-plane/tests/test_observability_stack.py, services/control-plane/tests/test_platform_manager_consoles.py, sdks/python/tests/test_packs.py, catalog/components/grafana.yaml, catalog/components/navin-manager-console.yaml, catalog/licence-exceptions.yaml.