helm: Add support for HorizontalPodAutoscaller on router #2843
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.
Description
This PR add new options in the Helm chart values allowing to deploy and HorizontalPodAutoscaler for the
router
component.This is basically the implementation of this part of the doc : https://fission.io/docs/installation/advanced-setup/#create-hpa-for-router-service
By default, nothing change for the user.
User can select the Kubernetes autoscaling
apiVersion
allowing support for user with cluster version under v1.23. By default theautoscalingApiVersion
used isautoscaling/v2
(support v1.23+ and required in v1.26+).The
router.autoscaling.metrics
handle the full metrics structure regardless of theapiVersion
.I have placed the value
autoscalingApiVersion
at the root allowing a reuse if we want to add autoscaling to other components of Fission in the futur.Which issue(s) this PR fixes:
Didn't find any
Testing
autoscaling.enabled=true
Checklist: