search

konflux-ci / architecture

Technical and Architecture documents
https://konflux-ci.dev/architecture/
18 stars 70 forks source link

Workspace Experience #187

Closed ralphbean closed 1 month ago

ralphbean commented 6 months ago

This is just a stub for now - I'm hoping to create a place where we can have a discussion and collect input.

dperaza4dustbit commented 6 months ago

In general, if we don't manage the workspace experience we have to assume user will be managing that, will be good to see how users are expected to manage their workspaces for the first release of konflux coming up without workspace support and then build the experience from there. My initial suggesting is to think of a workspace abstraction that can bring external dependencies like ArgoCD or KubeSaw as needed depending on the scale. This will keep a consistent experience for the user regardless if they are playing with Konflux in Kind or the are deploying on production with a multi-tenant and multi-cluster setup.

Having two experiences or as a result two APIs defeats the purpose of allowing user to play and gain perspective on what to expect in production.

ralphbean commented 1 month ago

Dropping this as the conversation is being driven by Gal and David in separate documents now.