Skip to content

Add agent in chart#48

Open
vehagn wants to merge 1 commit intonetbirdio:mainfrom
vehagn:add-agent
Open

Add agent in chart#48
vehagn wants to merge 1 commit intonetbirdio:mainfrom
vehagn:add-agent

Conversation

@vehagn
Copy link
Copy Markdown

@vehagn vehagn commented Mar 29, 2026

Signed-off-by: Vegard Hagen vegard@stonegarden.dev

Signed-off-by: Vegard Hagen <vegard@stonegarden.dev>
@jackylamhk
Copy link
Copy Markdown

Considering some may have more agent deployments in different VPCs than NetBird deployments, would it make more sense to separate the agent into its own chart?

@vehagn
Copy link
Copy Markdown
Author

vehagn commented Mar 29, 2026

I agree that separating the agent deployment into its own chart makes sense, though I figured with all the other deployments that can be enabled and disabled it didn't hurt too much.

In the monolithic deployment as in your PR it makes even more sense.

It's also somewhat less elegant having to first get the server and dashboard up and running to manually create a setup-key to use for the agent.

In a Kubernetes native deployment of NetBird it would be neat if this setup key could be automatically created as a Secret resource.

The slight downside of separating them in some maintenance overhead.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants