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
Dynamically add or remove plugins at build time (to reduce binary size)
Proposed Solution
Instead of packing plugins to binary, making per plugin per image, refer to kuberhealthy's daemonset-check. The plugin manager in Agent will also need some adjustments.
Alternatives Considered
Additional Context
The text was updated successfully, but these errors were encountered:
Yeah, The design decision not to create new pods for every test is deliberate. This is because when there are 1000s of tests, it puts a lot of load on the apiserver. So we wanted each test run and plugin to have relatively small costs in terms of compute and memory, as well as the number of requests to the api server. But there could be a compromise where you deploy a new plugin as a new pod, which gets invoked by pluginmanager at set intervals. Good suggestion!
Thank you for your contribution! This issue has been automatically marked as stale because it has no recent activity in the last 60 days. It will be closed in 7 days, if no further activity occurs. If this issue is still relevant, please leave a comment to let us know, and the stale label will be automatically removed.
Problem Statement
From the roadmap
Proposed Solution
Instead of packing plugins to binary, making per plugin per image, refer to kuberhealthy's daemonset-check. The plugin manager in Agent will also need some adjustments.
Alternatives Considered
Additional Context
The text was updated successfully, but these errors were encountered: