feat: Add replicas field to Function CRD for configurable deployment scaling #202
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.
Motivation
Currently, Function deployments are hardcoded to use 1 replica, which limits the ability to scale functions based on workload requirements. This change adds a configurable
replicas
field to the Function CRD, allowing users to specify the desired number of replicas for their function deployments. This enables horizontal scaling of functions to handle increased load and improve availability.Modifications
replicas
field toFunctionSpec
with validation and default value of 1FunctionReconciler
to use the specified replicas when creating deployments.DS_Store
and._*
files) to prevent accidental commitsThe implementation maintains backward compatibility by defaulting to 1 replica when the field is not specified, ensuring existing function deployments continue to work without modification.