8000 Make max concurrent reconciles configurable for agent and remaining controllers by weyfonk · Pull Request #3094 · rancher/fleet · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Make max concurrent reconciles configurable for agent and remaining controllers #3094

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

Merged
merged 3 commits into from
Dec 9, 2024

Conversation

weyfonk
Copy link
Contributor
@weyfonk weyfonk commented Nov 25, 2024

This makes max concurrent reconciles configurable, through worker counts, for reconcilers which had hard-coded counts in the Fleet controller (ie cluster, cluster group and imagescan reconcilers), and for reconcilers living in the agent.

The same default value (50) is used everywhere, although different values could make more sense as defaults, eg. a lower value for the drfit reconciler.

Refers to #2915.

Reconcilers for clusters, cluster groups and image scans now have
configurable `controller-runtime` worker counts, similarly to what is
already supported for gitrepo, bundle and bundle deployment reconcilers.
Fleet's cleanup logic does not make use of controller-runtime
reconcilers, hence does not need environment variables specifying how
many workers such reconcilers can use.
Reconcilers living in the Fleet agent now have configurable
`controller-runtime` worker counts, similarly to what is already
supported in the Fleet controller.
@weyfonk weyfonk requested a review from a team as a code owner November 25, 2024 13:49
@weyfonk weyfonk merged commit 910002d into rancher:main Dec 9, 2024
12 checks passed
weyfonk added a commit to weyfonk/fleet that referenced this pull request Dec 19, 2024
…ontrollers (rancher#3094)

* Make worker count configurable for cluster, clustergroup and imagescan

Reconcilers for clusters, cluster groups and image scans now have
configurable `controller-runtime` worker counts, similarly to what is
already supported for gitrepo, bundle and bundle deployment reconcilers.

* Remove workers env vars from cleanup container

Fleet's cleanup logic does not make use of controller-runtime
reconcilers, hence does not need environment variables specifying how
many workers such reconcilers can use.

* Make worker count configurable for agent reconcilers

Reconcilers living in the Fleet agent now have configurable
`controller-runtime` worker counts, similarly to what is already
supported in the Fleet controller.
manno pushed a commit that referenced this pull request Dec 20, 2024
* Make max concurrent reconciles configurable for agent and remaining controllers (#3094)

* Make worker count configurable for cluster, clustergroup and imagescan

Reconcilers for clusters, cluster groups and image scans now have
configurable `controller-runtime` worker counts, similarly to what is
already supported for gitrepo, bundle and bundle deployment reconcilers.

* Remove workers env vars from cleanup container

Fleet's cleanup logic does not make use of controller-runtime
reconcilers, hence does not need environment variables specifying how
many workers such reconcilers can use.

* Make worker count configurable for agent reconcilers

Reconcilers living in the Fleet agent now have configurable
`controller-runtime` worker counts, similarly to what is already
supported in the Fleet controller.

* Expose agent worker counts in fleet chart (#3152)

This enables agent worker counts to be configured when installing the
`fleet` chart, which is easier than tweaking individual releases of the
`fleet-agent` chart.
This still needs work to enable worker count updates through `helm
upgrade --reuse-values` though, as this updates the `fleet-agent`
`StatefulSet` _twice_, the second time with default values (50 workers
per reconciler).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants
0