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
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
The text was updated successfully, but these errors were encountered:
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.
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
The text was updated successfully, but these errors were encountered: