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

Setup of the Reconciler Operator Repository managing the Component Reconciliation inside SKR #9

Closed
Tracked by #8
adityabhatia opened this issue May 3, 2022 · 1 comment · Fixed by #1, #2, #3, #4 or #6
Closed
Tracked by #8
Assignees
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@adityabhatia
Copy link
Contributor

adityabhatia commented May 3, 2022

AC:

  • Create a Repository as first-prio for Iterating
  • POC for handling of component CRs via static clients
  • POC for handling of component CRs via dynamic clients
@adityabhatia
Copy link
Contributor Author

Comment from @Tomasz-Smelcerz-SAP
POC for handling of component CRs via static clients: The setup was verified to be working. There are two public sample repositories, one for the main Kyma Operator and the second one for a dummy Component Operator
The README.md files explain the repository structure and the golang modules split that we think will work fine for our purposes if we use static clients.
By static clients I mean golang level dependencies between modules - Kyma Operator is using golang clients with golang types imported from Component's projects.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment