Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Kpt Integration #204

Open
regicsolutions opened this issue Dec 21, 2022 · 2 comments
Open

Kpt Integration #204

regicsolutions opened this issue Dec 21, 2022 · 2 comments
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@regicsolutions
Copy link

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

@tumido
Copy link
Member

tumido commented Jan 5, 2023

Hi @regicsolutions,

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.

@sesheta
Copy link
Member

sesheta commented Apr 5, 2023

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.

/lifecycle stale

@sesheta sesheta added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

3 participants