Ways to help
Try it and tell us what breaks
Install on a spare server, deploy something real and open an issue with what you saw. Reports from real workloads are the most useful thing right now.
Pick a good first issue
Issues labeled good first issue and help wanted are scoped for newcomers. Read the contributing guide first for branch and commit conventions.
Improve the docs
Every docs page has an edit link. Fixes to unclear steps, missing flags and broken examples land fast.
Test multi-node
Enrollment, cordon and drain are verified against real Docker daemons. Cross-host transport and the WireGuard mesh need more real-world testing.
Talk to us
Ask a quick question in the Levelrail forum on the GLINR Discord, or start a GitHub discussion.
Star the repo
A star helps other operators find the project. It costs nothing and it does help.
At a glance
- Apache 2.0: license
- Go + React: stack
- 1 edition: no paid tier
Your first pull request
1
Open an issue first for anything bigger than a small fix
The reconciler, agent transport and database schema have deliberate design constraints worth discussing before you write code.
2
Branch and commit with the conventions
Branch names like fix/short-description and conventional commits. Hooks check formatting, lint, tests and dashes.
3
Keep each pull request to one logical change
Smaller, focused pull requests get reviewed faster.
Frequently asked questions
Do I need to sign a CLA?
Do I need to sign a CLA?
The contributing guide is the source of truth for contribution terms. Read it before opening your first pull request.
What languages is it written in?
What languages is it written in?
Go for the control plane and agent, and TypeScript with React for the dashboard.
Where do I report a security issue?
Where do I report a security issue?
Follow the security policy in the repository rather than opening a public issue.
Is there a roadmap?
Is there a roadmap?
Yes, the roadmap page lists phases and current status.