Finalize naming & clean up old stackable cockpit #47

Activity

1. lfrancke

   added this to Stackable End-to-End Coordinationon Mar 25, 2026
2. lfrancke

   moved this to Selected for Development in Stackable End-to-End Coordinationon Mar 25, 2026
3. labrenbe

   self-assigned this

   on Apr 2, 2026
4. labrenbe

   moved this from Selected for Development to In Progress in Stackable End-to-End Coordinationon Apr 2, 2026
5. labrenbe commented on Apr 9, 2026

   

   labrenbe

   on Apr 9, 2026

   Last edited by labrenbe

   Member

   More actions

   Before we can make a decision we should discuss if we want the backend for Stackable UI to stay SvelteKit or move to Rust

   Option 1 = backend for is Rust:
   backend code lives in stackable-cockpit repo, Svelte frontend replaces old frontend in web.

   Option 2 = backend stays SvelteKit
   Should move into own repo and probably reuse the stackable-cockpit name. The current backend = stackable-cockpitd becomes a utility/proxy to talk to Kubernetes. The stackable-cockpit repo is renamed to reflect the new role.
6. lfrancke commented on Apr 9, 2026

   

   lfrancke

   on Apr 9, 2026

   MemberAuthor

   More actions

   Having just learned my lesson from the Portal: It can become very painful having the two separate.
   Especially if the Backend is a "Backend for Frontend". I'd definitely keep that as SvelteKit. That could then talk to other backend bits like stackable-cockpitd as you mentioned
7. labrenbe commented on Apr 9, 2026

   

   labrenbe

   on Apr 9, 2026

   Member

   More actions

   I've discussed this with @Techassi today and we think this would be a good topic for the onsite week as there a pros and cons for both options. I've already added it to our agenda.
8. lfrancke

   closed this as completedon Jun 17, 2026
9. lfrancke

   moved this from In Progress to Done in Stackable End-to-End Coordinationon Jun 17, 2026