search

Jaydee94 / kubeseal-webgui

This is a simple web ui for Bitnami Sealed Secrets.
Apache License 2.0
75 stars 19 forks source link

[Enhancement Request] Dropdown Inclusion of Multiple Cluster Namespaces #238

Open ghost opened 9 months ago

ghost commented 9 months ago

In our setup, we synchronize all the instances of our Kubeseal clusters to a central one. We're interested in utilizing Kubeseal-webgui, but we're currently encountering an issue where only the namespaces from the main cluster appear in the dropdown menu. Ideally, we'd like to have visibility into namespaces from other clusters as well. One option could be manually populating them through a post endpoint, or preferably, using a service account to automatically retrieve a list of all namespaces across all clusters.

In the short term, having the ability to manually input our desired namespaces in the combo box would allow us to continue working with it effectively. We appreciate your consideration of this matter and would be grateful to hear your thoughts on possible solutions or alternatives.

Jaydee94 commented 9 months ago

Hey, @marc-andre-julien-uqam thanks for your feature request. I already thought of an kubeseal tenant approach in the past. One solution could be to deploy the UI component in a cluster. The API components could be deployed in multiple clusters and work as a satellite. After that we can implement a feature toggle to configure multiple tenants for the UI.. so you just need to configure the API endpoints of your satellite components.

@FSchumacher what do You think about this approach?

marcandjulien commented 8 months ago

Thank you, @Jaydee94, for your swift response to our feature request and for outlining such a forward-thinking solution. We've noticed your work on the multi-tenants branch, and it seems to align perfectly with what we're looking for. The approach of deploying the UI component in one cluster with the API components in multiple clusters as satellites, along with the feature toggle for configuring multiple tenants, is precisely the kind of solution we had hoped for. We're truly grateful for the effort and creativity you've put into addressing our needs.

Our team has scheduled to implement and test this multi-tenant setup in April due to our current commitments. We are genuinely excited about the potential improvements this will bring to our Kubeseal clusters' synchronization and namespace visibility. Rest assured, we will share our experiences, feedback, and any additional insights we gather as we proceed with this implementation.

Once again, thank you for your dedication and hard work on enhancing the kubeseal-webgui. Your contributions are highly valued by our team and undoubtedly by the broader community as well.

Jaydee94 commented 8 months ago

Hi @marcandjulien the pull request which is linked to this issue just needs to be reviewed. In my testing envrionments the multi tenant setup works as desired.

I hope we can release the new version soon. Please be patient as we are only two active developers of this project.

Best regards.