cleanup edge onboarding process for NATS #878

New issue

Open

opened 2026-03-28 04:29:29 +00:00 by mfreeman451 · 0 comments

mfreeman451 commented

2026-03-28 04:29:29 +00:00

Owner

Imported from GitHub.

Original GitHub issue: #2537
Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/issues/2537
Original created: 2026-01-27T07:31:32Z

Describe the bug

https://192.168.2.235/admin/collectors

The Provisioning NATS Account progress spinner spins indefinitely and none of this stuff seems to be working anymore. We initially created most of this when we were trying to figure out how to do multi-tenancy, we first had attribute-based/row level tenancy, then we tried schema based but we still had a shared serviceradar-core and web-ng control plane, to today where we will provision separate instances of ServiceRadar per tenant, isolated by namespaces, or just support an on-prem/OSS user with a single-tenant installation on k8s or docker, and every tenant, even in a single-tenant situation, gets their own credentials to CNPG and a NATS account (JWT).

We need to think a little harder about what this should look like or what the purpose of this really is. From the perspective of a tenant that doesn't care about tenancy, and since ServiceRadar (SR) isn't really multi-tenant anymore, the SaaS will have a control-plane that will provision new tenants in their own namespace, with their own CNPG account connecting to a shared CNPG cluster, and their own NATS account, also connecting to a shared NATS cluster. Maybe all we really need to worry about right now is the single-tenant scenario on k8s or docker deployments and break down the steps where we interact with NATS:

User story

User downloads and installs SR in either docker or kubernetes (includes SR, CNPG, NATS, etc)
SR installation creates new CNPG user/credentials, user sees everything under platform schema
SR installation creates new NATS account/JWT
User decides that they want to deploy a NATS Leaf server in their edge network, connected to their cluster or docker compose NATS "hub"
User performs edge-onboarding process for NATS Leaf in SR UI

I'm not really sure why this thing thinks there is something being provisioned and if that is actually true or not, this is a clean system, I haven't tried to add a NATS leaf yet.

To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

Imported from GitHub. Original GitHub issue: #2537 Original author: @mfreeman451 Original URL: https://github.com/carverauto/serviceradar/issues/2537 Original created: 2026-01-27T07:31:32Z --- **Describe the bug** https://192.168.2.235/admin/collectors The `Provisioning NATS Account` progress spinner spins indefinitely and none of this stuff seems to be working anymore. We initially created most of this when we were trying to figure out how to do multi-tenancy, we first had attribute-based/row level tenancy, then we tried schema based but we still had a shared `serviceradar-core` and web-ng control plane, to today where we will provision separate instances of ServiceRadar per tenant, isolated by namespaces, or just support an on-prem/OSS user with a single-tenant installation on k8s or docker, and every tenant, even in a single-tenant situation, gets their own credentials to `CNPG` and a NATS account (JWT). We need to think a little harder about what this should look like or what the purpose of this really is. From the perspective of a tenant that doesn't care about tenancy, and since ServiceRadar (SR) isn't really multi-tenant anymore, the SaaS will have a control-plane that will provision new tenants in their own namespace, with their own CNPG account connecting to a shared CNPG cluster, and their own NATS account, also connecting to a shared NATS cluster. Maybe all we really need to worry about right now is the single-tenant scenario on k8s or docker deployments and break down the steps where we interact with NATS: User story 1. User downloads and installs SR in either docker or kubernetes (includes SR, CNPG, NATS, etc) 2. SR installation creates new CNPG user/credentials, user sees everything under `platform` schema 3. SR installation creates new NATS account/JWT 4. User decides that they want to deploy a NATS Leaf server in their edge network, connected to their cluster or docker compose NATS "hub" 5. User performs edge-onboarding process for NATS Leaf in SR UI <img width="1233" height="668" alt="Image" src="https://github.com/user-attachments/assets/1a55614c-63a8-4502-a8a8-25fb1e1fb654" /> I'm not really sure why this thing thinks there is something being provisioned and if that is actually true or not, this is a clean system, I haven't tried to add a NATS leaf yet. **To Reproduce** Steps to reproduce the behavior: 1. Go to '...' 2. Click on '....' 3. Scroll down to '....' 4. See error **Expected behavior** A clear and concise description of what you expected to happen. **Screenshots** If applicable, add screenshots to help explain your problem. **Desktop (please complete the following information):** - OS: [e.g. iOS] - Browser [e.g. chrome, safari] - Version [e.g. 22] **Smartphone (please complete the following information):** - Device: [e.g. iPhone6] - OS: [e.g. iOS8.1] - Browser [e.g. stock browser, safari] - Version [e.g. 22] **Additional context** Add any other context about the problem here.