--- # nocheck: seaweedfs-required - Checkmk Raw bundles its own monitoring core + RRD storage on a single OMD-site volume; it has no object-store surface. sso: bond: 1 enabled: "{{ 'web-app-keycloak' in group_names }}" shared: "{{ 'web-app-keycloak' in group_names }}" flavor: oauth2 oauth2: origin: host: checkmk port: "5000" acl: whitelist: - /cmk/check_mk/api/ # nocheck: playwright-service-flag - identity backend (LDAP connection synced into the site); login is driven through the oauth2 gate, so there is no separate LDAP Playwright surface. ldap: bond: 1 enabled: "{{ 'svc-db-openldap' in group_names }}" shared: "{{ 'svc-db-openldap' in group_names }}" logout: bond: 1 enabled: "{{ 'web-svc-logout' in group_names }}" shared: "{{ 'web-svc-logout' in group_names }}" dashboard: bond: 1 enabled: "{{ 'web-app-dashboard' in group_names }}" shared: "{{ 'web-app-dashboard' in group_names }}" matomo: bond: 1 enabled: "{{ 'web-app-matomo' in group_names }}" shared: "{{ 'web-app-matomo' in group_names }}" email: bond: 1 enabled: "{{ MAIL_PROVIDER in group_names }}" shared: "{{ MAIL_PROVIDER in group_names }}" css: bond: 1 enabled: "{{ 'web-svc-css' in group_names }}" shared: "{{ 'web-svc-css' in group_names }}" # nocheck: dynamic-flag - gated on services.sso.enabled, not on group_names # nocheck: playwright-service-flag - runtime DOM patch (injected logout), no probe-able surface flag javascript: bond: 1 enabled: "{{ lookup('config', 'web-app-checkmk', 'services.sso.enabled') | bool }}" shared: "{{ lookup('config', 'web-app-checkmk', 'services.sso.enabled') | bool }}" prometheus: bond: 1 enabled: "{{ 'web-app-prometheus' in group_names }}" shared: "{{ 'web-app-prometheus' in group_names }}" # nocheck: playwright-service-flag self-provider checkmk: enabled: true shared: true bond: 1 site: cmk healthcheck: flavor: curl path: cmk/check_mk/login.py modes: compose: enabled: true swarm: enabled: true # nocheck: default-placement-manager stateful OMD site is node-local (OMD fcntl locks return EBADF on NFS); pin so the task never leaves the node holding its data placement: manager # nocheck: single-replica replicas: 1 cpus: 2.0 mem_reservation: 1g mem_limit: 2g pids_limit: 2048 min_storage: 1053MB image: checkmk/check-mk-raw version: "2.4.0p39" backup: no_stop_required: true name: checkmk ports: internal: http: 5000 agent: 8000 local: http: 8087 sso: 16509 agent: 8500 onion: # nocheck: onion-flag the monitoring server dials its agents, so nothing connects inward here, and the agent speaks no authentication of its own agent: false run_after: - web-app-keycloak - svc-db-openldap lifecycle: beta # nocheck: playwright-service-flag # nocheck: variants-coverage — sso-variant-tor requires the onion on in every variant, so the false polarity has no variant left to live in tor: bond: 0.5 enabled: "{{ 'svc-net-tor' in group_names }}" shared: true # nocheck: dynamic-flag # nocheck: dynamic-flag - gated on services.sso.enabled, not on group_names # nocheck: playwright-service-flag, dynamic-flag infrastructure backup consumer container_backup: # nocheck: bond-baseline backup host joins outside the variant topology bond: 1 enabled: "{{ 'svc-bkp-volume-2-local' in group_names }}" shared: true # nocheck: playwright-service-flag internal adapter sidecar, covered by the role's MCP guest spec # nocheck: dockerfile-custom the Dockerfile is owned by svc-ai-mcp-adapter and staged per instance, so every adapter-backed provider shares one audited build # nocheck: dynamic-flag the sidecar tracks this role's own mcp flag, not another role's presence; a group_names expression would decide its exposure from an unrelated deployment checkmkmcp: enabled: "{{ lookup('config', 'web-app-checkmk', 'mcp.enabled') | bool }}" shared: false image: python # nocheck: docker-version base of the self-built stdlib adapter, not the served application version: "3.13.15-slim" custom: true name: checkmkmcp cpus: "0.25" mem_reservation: 16m mem_limit: 24m pids_limit: 64 ports: internal: http: 8080 # nocheck: playwright-service-flag MCP pairing is proven by the role's own MCP spec, not by a per-consumer gate openwebui: bond: 0.5 enabled: "{{ 'web-app-openwebui' in group_names }}" shared: "{{ 'web-app-openwebui' in group_names }}" # nocheck: playwright-service-flag MCP pairing is proven by the role's own MCP spec, not by a per-consumer gate hermes: bond: 0.5 enabled: "{{ 'web-app-hermes' in group_names }}" shared: "{{ 'web-app-hermes' in group_names }}" # nocheck: playwright-service-flag MCP pairing is proven by the role's own MCP spec, not by a per-consumer gate openclaw: bond: 0.5 enabled: "{{ 'web-app-openclaw' in group_names }}" shared: "{{ 'web-app-openclaw' in group_names }}" # nocheck: playwright-service-flag MCP pairing is proven by the role's own MCP spec, not by a per-consumer gate # nocheck: dynamic-flag the entry refuses this client, so the link is off on every host and no group_names gate can decide it flowise: enabled: false shared: false mcp_consumer: false