You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
thanks for this suggestion! This Backstage instance is focused on the Operate First Community Cloud and it seems we don't have all the necessary facilities to deploy this. I think that makes configuring the backend part of this plugin impossible.
What is your desired usecase with this? What would you like to achieve by deploying kpt plugin here?
Current limitations I see here are:
Operate First Community cloud doesn't have any centralized OIDC/auth provider providing OpenShift tokens for individual clusters
The plugin seems to require fixed namespace selector which doesn't suite the multi-tenant nature of our clusters
no config-sync deployed
I think it would be nice to experiment with this, however it doesn't seem to be fit our deployment method of 1 Backstage instance watching multitude of clusters where each cluster has their tenants isolated into team-owned namespaces.
If we can overcome these issues I think this plugin would be a nice addition here.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Additional context
It would be great to have kpt integration
pre-requisites can be found here
Acceptance Criteria
Integration with Open Source Kpt Configuration as Data Plugins: kpt backstage plugins
Relevant links
No response
The text was updated successfully, but these errors were encountered: