-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Minimal hub home-setup #7
Comments
hey @AliveDevil thanks for the information. I'm actually working on this for the moment, and exactly good documentation is missing (and some changes were required). I'm still working this out but believe I would be able to have something well documented and working EOW - early next week. Will come back on your questions as well. |
Sounds good, looking forward to the improved documentation :) |
Currently have some spare time to check on deploying this again using Docker exclusively (no Kubernetes) …
using |
Hey,
I'm trying to setup Kerberos for the third or fourth time now, without really knowing how these components work together - never really got anywhere - something always broke.
In case I want to setup a self-contained, not publicly exposed Kerberos Hub setup (for monitoring some cameras, with timeline/scrubbing, central view, live ML object detection), what's the absolute minimum of services I need to install, to get this rolling?
From what I could scrape together in the helm-charts repository and here:
Now, in the helm-charts repository are a bunch of added services:
Which of these is necessary to get live-detection and record-detection?
There are some things I don't quite get with the dataflow from the agent to hub/vault - do agents need to forward to the vault first, or is this only really necessary, when forwarding from an edge vault to a cloud hub?
I.e. is
Agent -> Hub <-> Vault
as minimal configuration usable, or will this always beAgent -> Vault <-> Hub
(is this single-vault setup even possible)?I've found at least two different queues for the initial ingest of events: kcloud-event-queue, data-filtering.
What difference does it make when configuring Vault to do edge or cloud detection?
In both, deployment and helm-charts, is sample MongoDb data, but when creating an account with
POST /account/user/create
and the admin api key, the subscriptions-table isn't populated, but a nested subscription object used in the user table, what's up with that?Is it possible to define different retention periods, for different artifacts? e.g. recordings, that are analyzed and triggered an event due to motion/object detection should be retained for a week, all other recordings should be dropped within a day.
Is
superseding
The text was updated successfully, but these errors were encountered: