Is your feature request related to a problem? Please describe.
Some people may prefer to use KEDA for scaling for various reasons. For example:
- already have the KEDA External Metrics Provider in their cluster, and therefore are not able to install another metrics adapter as the External Metrics Provider in the same cluster
- already use KEDA Temporal trigger for unversioned workers, and want to migrate to controller-supported versioning without changing their scaling resources
Describe the solution you'd like
kedacore/keda#7672 adds support for Worker Deployment Versioning to KEDA temporal trigger.
The WorkerResourceTemplate templating code in the worker controller will need to populate the new workerDeploymentName and workerDeploymentBuildId fields for each per-version KEDA ScaledObject it creates.
It will also need to fill in the scaleTargetRef of the KEDA ScaledObject with the per-version k8s Deployment name (might already do this, but need to test).
Additional context
We should also decide whether KEDA ScaledObject should be a white-listed resource in the default value for workerResourceTemplate.allowedResources. That is optional.
Is your feature request related to a problem? Please describe.
Some people may prefer to use KEDA for scaling for various reasons. For example:
Describe the solution you'd like
kedacore/keda#7672 adds support for Worker Deployment Versioning to KEDA
temporaltrigger.The
WorkerResourceTemplatetemplating code in the worker controller will need to populate the newworkerDeploymentNameandworkerDeploymentBuildIdfields for each per-version KEDA ScaledObject it creates.It will also need to fill in the
scaleTargetRefof the KEDA ScaledObject with the per-version k8s Deployment name (might already do this, but need to test).Additional context
We should also decide whether KEDA ScaledObject should be a white-listed resource in the default value for
workerResourceTemplate.allowedResources. That is optional.