Skip to content

Decouple flows (api, cli, ui) #353

Description

@mjudeikis

When dealing with kube-bind mini-ecosystem I want to be able to do the following:

  1. Use only kube-bind API and bring my own UI (or be part of bigger UI for smooth UX/DX)
  2. Use my own CLI and use everything else
  3. Be able to interact with kube-bind in full-gitops mode, without even knowing about UI,CLI, or backend.

This leads to need to split into 3 parts:

  1. Backend is full API compatible (/api/{methods})
  2. Backend supports OIDC authentication flow (optional, requires Add embedded oidc #349)
  3. UI is embedded into backend as SPA but with the option to run without web OR provide your own (by either hot swapping in the image by layer or simple --frontend http://frontend.svc:3000 when running backend
  4. Allow full GitOps flow where the user creates Request objects and applies them to the right clusters.

4th might require more work and potentially should be split to separate stories, but when doing 1-3, one needs to think about this.

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request
No fields configured for Feature.

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions