-
Notifications
You must be signed in to change notification settings - Fork 82
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
infrastructure flow reconciler #739
Conversation
/hold |
c43b2fb
to
3ca4f7e
Compare
Testrun: e2e-dtd7r +---------------------+---------------------------+-----------+----------+ | NAME | STEP | PHASE | DURATION | +---------------------+---------------------------+-----------+----------+ | infrastructure-test | infrastructure-test | Failed | 41m27s | | infrastructure-test | infra-flow-test | Failed | 32m3s | | infrastructure-test | infra-flow-migration-test | Failed | 43m29s | | bastion-test | bastion-test | Succeeded | 11m11s | +---------------------+---------------------------+-----------+----------+ |
Testrun: e2e-6jrp7 +---------------------+---------------------------+-----------+----------+ | NAME | STEP | PHASE | DURATION | +---------------------+---------------------------+-----------+----------+ | bastion-test | bastion-test | Succeeded | 10m46s | | infrastructure-test | infrastructure-test | Failed | 44m2s | | infrastructure-test | infra-flow-test | Failed | 41m38s | | infrastructure-test | infra-flow-migration-test | Failed | 46m32s | +---------------------+---------------------------+-----------+----------+ |
bad7a3f
to
d40f2cb
Compare
Testrun: e2e-lrwn4 +---------------------+---------------------------+-----------+----------+ | NAME | STEP | PHASE | DURATION | +---------------------+---------------------------+-----------+----------+ | bastion-test | bastion-test | Succeeded | 12m53s | | infrastructure-test | infrastructure-test | Succeeded | 34m35s | | infrastructure-test | infra-flow-test | Succeeded | 27m20s | | infrastructure-test | infra-flow-migration-test | Failed | 35m34s | +---------------------+---------------------------+-----------+----------+ |
/test |
Testrun: e2e-dhp5m +---------------------+---------------------------+-----------+----------+ | NAME | STEP | PHASE | DURATION | +---------------------+---------------------------+-----------+----------+ | bastion-test | bastion-test | Succeeded | 12m22s | | infrastructure-test | infra-flow-migration-test | Succeeded | 33m54s | | infrastructure-test | infrastructure-test | Succeeded | 31m58s | | infrastructure-test | infra-flow-test | Succeeded | 27m4s | +---------------------+---------------------------+-----------+----------+ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we try to unify whiteboard and inventory as the state of the whiteboard is also persisted for other providers like AWS and Openstack?
Looks to me as if we have resource ids and other data in whiteboard and inventory with sometimes overlapping purposes:
- managed items (created by the infrastructure controller), persisted for providing a list of managed resources in case for manual cleanup on forced deletion
- managed or looked up resource ids and names exposed for third-party controllers.
- managed resource ids/names in state if there is no suitable place to store this information on IaaS side (like tags, etc)
- managed resource ids/names in state for informative purposes
- internal caching of resource object details to simplify code
thanks for the headsup @kon-angelo. Happy to see it alive! 🚀 Could you co-author me if possible in the merge commit? |
Co-authored-by: Adrian Stobbe <[email protected]>
d40f2cb
to
cf5e02b
Compare
/test |
Testrun: e2e-rmp4j +---------------------+---------------------------+-----------+----------+ | NAME | STEP | PHASE | DURATION | +---------------------+---------------------------+-----------+----------+ | bastion-test | bastion-test | Succeeded | 11m23s | | infrastructure-test | infrastructure-test | Succeeded | 33m40s | | infrastructure-test | infra-flow-test | Succeeded | 30m47s | | infrastructure-test | infra-flow-migration-test | Succeeded | 35m0s | +---------------------+---------------------------+-----------+----------+ |
@MartinWeindel I reimplemented the inventory on top of the whiteboard. The reason the inventory had a separate implementation rather just storing the IDs, is that it has a bit of special logic with regards to additions/deletions that would not apply for other providers. So pushing more tight integration doesn't make sense from my view. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
Thanks to @elchead for all the initial work and @kon-angelo for taking care of for both the big picture and all the details.
How to categorize this PR?
/area control-plane
/kind enhancement
/platform azure
What this PR does / why we need it:
This is a continuation from #596. Special thanks to @elchead for all the effort in the initial implementation 💯
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Release note: