(feat) Add EvaluateIndependently field to HealthCheckSpec#603
Merged
gianlucam76 merged 1 commit intoprojectsveltos:mainfrom Feb 7, 2026
Merged
(feat) Add EvaluateIndependently field to HealthCheckSpec#603gianlucam76 merged 1 commit intoprojectsveltos:mainfrom
gianlucam76 merged 1 commit intoprojectsveltos:mainfrom
Conversation
This PR introduces the `EvaluateIndependently` field to the HealthCheck API. This field serves as a hint to the controller that resources can be processed in smaller batches (chunks) rather than loading the entire set into the Lua engine at once. Currently, all resources matched by a selector are passed into a single Lua resources table. In large-scale environments, converting thousands of Kubernetes objects into Lua tables simultaneously causes massive memory spikes, often leading to OOM (Out of Memory) kills for the agent. - **When false**: The controller maintains existing behavior, passing all resources at once. This is required for scripts that perform cross-resource analysis (e.g., "Are at least 3 replicas of this app healthy?"). - **When true**: The controller is authorized to split the resource list into chunks (e.g., 50 at a time). This significantly lowers the memory ceiling because the Lua heap only needs to hold a small subset of data during each iteration.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR introduces the
EvaluateIndependentlyfield to the HealthCheck API. This field serves as a hint to the controller that resources can be processed in smaller batches (chunks) rather than loading the entire set into the Lua engine at once.Currently, all resources matched by a selector are passed into a single Lua resources table. In large-scale environments, converting thousands of Kubernetes objects into Lua tables simultaneously causes massive memory spikes, often leading to OOM (Out of Memory) kills for the agent.
When false: The controller maintains existing behavior, passing all resources at once. This is required for scripts that perform cross-resource analysis (e.g., "Are at least 3 replicas of this app healthy?").
When true: The controller is authorized to split the resource list into chunks (e.g., 50 at a time). This significantly lowers the memory ceiling because the Lua heap only needs to hold a small subset of data during each iteration.