Hub API and frontend now gate passkeys behind FEATURE_PASSKEYS_ENABLED.
kerberoshub.api.passkeys.enabled sets it to "true" on Hub API alongside
the passkey configuration, and passes the same value to the frontend and
demo frontend, so one switch turns passkeys on or off everywhere.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Publish opt-in hardened runtime support with named Admin Service routing, configurable health probes, legacy defaults and runtime regression coverage.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Retain default Admin port 80 while allowing 8080 and explicit container security settings. Add notification-only pod and container contexts without changing its provider or FFmpeg contract. Cover routing, tmpfs, TLS, identity, default preservation and per-component isolation.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* feat(hub): make the dominant color stage opt-in
Add kerberospipeline.dominantColor.enabled (default false). It gates the
pipe-dominantcolor deployment and is projected to pipe-analysis as
DOMINANTCOLOR_ENABLED, so the producer and consumer follow one value.
Requires a hub-pipeline-analysis image that reads DOMINANTCOLOR_ENABLED:
older images always publish to kcloud-dominantcolor-queue.fifo, which
would back up once the consumer is removed.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore(hub): bump analysis to v1.8.22 for DOMINANTCOLOR_ENABLED
v1.8.22 is the first hub-pipeline-analysis release that reads the flag
(uug-ai/hub-pipeline-analysis#114). Chart version moves to 0.159.0 since
0.158.0 was taken on main.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* Add optional pipeline Deployment annotations and sync-wave examples
Expose empty-by-default annotation maps per pipeline service and an opt-in waves 10-70 example. Include a standalone Helm render check; CI workflow wiring is deferred due credential scope.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
* Keep sync-wave examples inline with each service
Remove the separate overlay and make render checks supply per-service overrides directly. Leave optional defaults and Deployment template support unchanged.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
---------
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
- Add kerberoshub.frontend.features.liveview.hlsEnabled (default true) and
wire it as FEATURE_HLS_ENABLED on hub-frontend and hub-frontend-demo. When
'false' the front-end removes the HLS live-transport option.
- Replace the bundled anpr example stage/worker with a commented-out
hub-loitering example; the chart now ships no enabled custom stage by
default (stages are values-only, opt-in).
- Update the generic hub-stage comment to the loitering example.
- Make the queue-consistency check self-contained: it synthesises a neutral
throwaway stage ('queuecheck') via --set instead of relying on a bundled
example worker.
NOTE: Chart.yaml version intentionally not bumped — repo version/tag state is
already inconsistent (Chart.yaml 0.117.0 vs tags up to hub-0.119.0); pick the
next version at release time.