Current KubeStellar Plugin Limitations and Required Improvements

[MAVRICK-1]

Current KubeStellar Plugin Limitations and Required Improvements

The current KubeStellar plugin cannot store data or interact with internal APIs and other functionality. Following an architecture similar to ArgoCD for reduced dependencies, we must enable:

1. Database Integration

   • Database sharing capabilities
   • Database access functionality

2. API Access and Endpoints

   • Create endpoints that interact with internal APIs
   • Enable full API access

3. Enhanced Development Workflow

   • Provide applications where users can develop directly through code
   • Eliminate the current cumbersome process of writing code, creating tar files, and then uploading them
   • This is particularly difficult for complex projects

4. Dashboard Capabilities

   • Allow users to add custom dashboards
   • Enable data point configuration for Grafana dashboards

5. Plugin Extensibility

   • Make the system more plugin-capable

6.Interaction with other component

7. Follow helm chart architecture to add and remove plugin

Required redesign

[MAVRICK-1]

cc @clubanderson @btwshivam @naman9271 @oksaumya

[clubanderson]

I really like the idea of cross component interaction. Do you also intend for this to allow cross plugin interaction? 2 or more plugins can interact with each other? And some plugins may only want to interact with certain other plugins (for private and semi-private plugins)

also - have you thought through paid/unpaid implications to your ideas. Also - versioning will play a big role as well I think - no?

[MAVRICK-1]

Yes, most of that is correct. For versioning, we will follow the Helm chart architecture. In simple terms, it will function like a custom controller for the KubeStellar UI.

[clubanderson]

ok - so lets get some real users to comment here