-
Notifications
You must be signed in to change notification settings - Fork 206
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
refactor: persist collectors memory settings in collectorsgroup CRD (#…
…1824) This PR makes it so: - calculated memory settings for collectors are calculated and written in collectors group CRD by the scheduler. - The values can be easily seen where the blong logically, in each collectors group. - after the refactor, auto scaler no longer depends or watches the odigos config resource in case it changes. - any changes to the memory settings are updated in the collector group CRD which autoscaler already watch and reconcile. It aim to simplify the reconciliation processes in autoscaler, and make it depend on one less resource. any config computations are offloaded to scheduler and should trigger autoscaler less. This PR is pure refactor and does not change any existing behavior. follow up PRs will introduce changes, additions, and applying memory settings also in node collector.
- Loading branch information
Showing
16 changed files
with
242 additions
and
97 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
65 changes: 65 additions & 0 deletions
65
api/generated/odigos/applyconfiguration/odigos/v1alpha1/collectorsgroupmemorysettings.go
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
13 changes: 11 additions & 2 deletions
13
api/generated/odigos/applyconfiguration/odigos/v1alpha1/collectorsgroupspec.go
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.