Replies: 1 comment 1 reply
|
This is good idea, but I'd like to keep sofka opensource and just a tui for now, as I do not plan to monetize it :) |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
feat: P3: sofka lib as server, that allow support / dev people to reach Kube cluster over Web with all possible guardrails and zero chance to spam API (as it will communicate to cluster) and airgap support
(I believe most of current tools will require internet connection)
so it gets the data every 10 sec or stream, but 100 devs / support / monitoring people can connect to sofka not as TUI but as a backend server and do what ever they like to do in read only, and maybe 1h requests in future for some actual changes
with rust/tokio/axum/flatbuffers or rkyv/zero copy/quic or ws, Svelte for frontend, will be amazing tech
headlamp is a proxy, it does not share the state like sofka can
can be one of the monetization ways in future, like first 5-10 free then 10$/mo/seat
OR
probably even WEB open core (AGPL) + some modules under sub (like gitlab etc) will be the best patch
compliance, SSO can be gated as usual
sofka backend will stay on MIT/Apache 2.0 for obvious reasons
All reactions