-
Notifications
You must be signed in to change notification settings - Fork 81
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
Ensure peer-pods deployment is complete w.r.to webhook and VM resource limits #1976
Comments
Can we look at those questions individually or are they inherently coupled? I think with regards to cloud resource management |
We can look at it individually. |
Raised a PR to remove peerpodconfig-ctrl #2027 This PR in isolation is not of much use unless the webhook is also deployed as part of the install to ensure there is a max limit to the number of cloud instances that can be created by cloud-api-adaptor. |
Currently the default operator based deployment doesn't deploy the complete stack
The following diagram shows the high level resource accounting and management for peer-pods
Ref: old deck on the resource accounting and management for peer-pods - https://docs.google.com/presentation/d/1GWNgQdRC5WxrXz_0XCW3DGIfzQHkO4MaN-8BlRPuTDc/edit#slide=id.g13a9839f269_0_0
The node extended resources are advertised by the peerpodconfig-ctrl. The earlier intention was to use peerpodconfig-ctrl to deploy all the required components for cloud-api-adaptor, but we are not yet there. This delay in implementation also gives us an opportunity to re-think the right approach.
Few questions that comes to my mind:
Additionally there is the issue deploying all the components via operator. There is some initial work that has happened it has created issues in the past with the release and test workflow. So this needs to be re-looked as well.
I'm starting this issue to kickstart the discussion so that we can address this important issue for the 0.10.0 release
cc @yoheiueda @mkulke @stevenhorsman @snir911 @huoqifeng
The text was updated successfully, but these errors were encountered: