We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Description
KIM will become a critical component of the Kyma backend and be responsible for any infrastructure (especially cluster creation) related tasks.
We see already a growing amount of expectations and requirements for KIM. This requires a well defined architecture which supports
Take already known requirements into consideration when designing the new architecture:
AC:
Create ADRs for KIM which show how the software architecture will look like
When ADR is merged, close following issues:
Implement a POC of the ADR and demonstrate it to the team - PoC that creates gardener cluster when CR is created akgalwas/infrastructure-manager#1
The text was updated successfully, but these errors were encountered:
We might have some overlap with https://github.com/kyma-project/kyma-environment-broker/blob/main/docs/user/01-10-architecture.md
Sorry, something went wrong.
Closing, as the ADR was merged.
akgalwas
No branches or pull requests
Description
KIM will become a critical component of the Kyma backend and be responsible for any infrastructure (especially cluster creation) related tasks.
We see already a growing amount of expectations and requirements for KIM. This requires a well defined architecture which supports
Take already known requirements into consideration when designing the new architecture:
AC:
Create ADRs for KIM which show how the software architecture will look like
When ADR is merged, close following issues:
Implement a POC of the ADR and demonstrate it to the team - PoC that creates gardener cluster when CR is created akgalwas/infrastructure-manager#1
The text was updated successfully, but these errors were encountered: