feat: onboarding agents #625

New issue

Closed

opened 2026-03-28 04:26:35 +00:00 by mfreeman451 · 1 comment

mfreeman451 commented

2026-03-28 04:26:35 +00:00

Owner

Imported from GitHub.

Original GitHub issue: #1899
Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/issues/1899
Original created: 2025-10-28T00:07:54Z

Is your feature request related to a problem?

Edge-deployed agents should be easy to deploy. When a user installs an agent, typically using a bare-metal package (serviceradar-sysmonvm), they need a way to onboard it so it can connect through the spire-agent to the spire server and get its mTLS certs.

admin UI (RBAC) for adding new agents
serviceradar-cli for adding new agents

Both tools should generate some key or something that a user can supply to the package when they're installing it, this should be used once and then invalidated, should also probably have a timer/expiry on it.

The agent should not have to talk directly to the core for any of this to work if possible.

Describe the solution you'd like

A clear and concise description of what you want to happen.

Describe alternatives you've considered

A clear and concise description of any alternative solutions or features you've considered.

Additional context

Add any other context or screenshots about the feature request here.

Imported from GitHub. Original GitHub issue: #1899 Original author: @mfreeman451 Original URL: https://github.com/carverauto/serviceradar/issues/1899 Original created: 2025-10-28T00:07:54Z --- **Is your feature request related to a problem?** Edge-deployed agents should be easy to deploy. When a user installs an agent, typically using a bare-metal package (serviceradar-sysmonvm), they need a way to onboard it so it can connect through the spire-agent to the spire server and get its mTLS certs. - [ ] admin UI (RBAC) for adding new agents - [ ] serviceradar-cli for adding new agents Both tools should generate some key or something that a user can supply to the package when they're installing it, this should be used once and then invalidated, should also probably have a timer/expiry on it. The agent should not have to talk directly to the core for any of this to work if possible. **Describe the solution you'd like** A clear and concise description of what you want to happen. **Describe alternatives you've considered** A clear and concise description of any alternative solutions or features you've considered. **Additional context** Add any other context or screenshots about the feature request here.

mfreeman451 commented

2026-03-28 04:26:36 +00:00

Author

Owner

Imported GitHub comment.

Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/issues/1899#issuecomment-3813914603
Original created: 2026-01-28T21:01:47Z

closing, stale

Imported GitHub comment. Original author: @mfreeman451 Original URL: https://github.com/carverauto/serviceradar/issues/1899#issuecomment-3813914603 Original created: 2026-01-28T21:01:47Z --- closing, stale