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

Move EDP tenant registration logic to KMC #90

Open
a-thaler opened this issue Sep 20, 2024 · 1 comment
Open

Move EDP tenant registration logic to KMC #90

a-thaler opened this issue Sep 20, 2024 · 1 comment
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

Comments

@a-thaler
Copy link
Collaborator

a-thaler commented Sep 20, 2024

Description

At the moment, KEB and KMC have a dependency to EDP. Even worse, if KEB was not doing its job, KMC will fail to push data to EDP. See also the arch diagram.

Moving this dependency fully to KMC will make KMC more self-contained and simplifies KEB, but also will speed up the base provisioning process of a cluster via KEB.

After #89 is realized, this task should be fairly simple to realize by using the existing client for EDP to call the de/provisioning of a subaccount whenever the billing decision for a cluster is swapping.

Goal: Add the EDP tenant de/provisioning process to KMC

Criterias

  • Whenever there is a new cluster to be billed, the tenant gets onboarded at EDP. On success the info gets stored maybe as finalizer on the Runtime CR
  • Whenever there is a cluster to unbill, the tenant gets offboarded and the finalizer removed
Copy link

github-actions bot commented Dec 1, 2024

This issue has been automatically marked as stale due to the lack of recent activity. It will soon be closed if no further activity occurs.
Thank you for your contributions.

@a-thaler a-thaler added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale labels Dec 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
Development

No branches or pull requests

1 participant