feat: New ScalingSet CRD to deploy isolated interceptors+scalers #1014

0 / 2 tasks completed

2 tasks still to be completed

Task	Status
Commits are signed with Developer Certificate of Origin (DCO)	Incomplete
Changelog has been updated and is aligned with our changelog requirements	Incomplete
`README.md`	Incomplete
The `docs/` directory	Incomplete
The docs repo	Incomplete
Documentation	Incomplete
CRD Status propagation	Incomplete
Autoscaling	Incomplete
Support for global configurations (timeouts, TLS, watched namespaces, etc...)	Incomplete
kube-api rejects some resource creation	Incomplete
failure to form the `externalScalerURI`	Incomplete
interceptor/scaler are not running with desired replica count and/or are unhealthy	Incomplete
possibly getting some basic stats from interceptor admin endpoint?	Incomplete
static - a single interceptor+scaler without scalingsets enabled (the current v0.8.0 workflow)	Incomplete
dynamic - enable scalingsets CRD and this broad RBAC	Incomplete
The operator always lists all ScalingSets in the cluster, but the actual permission to create/update/delete deployments depends on RBAC scoping.	Incomplete
For a minimal-scoped approach, create Roles/RoleBindings for each namespace of interest.	Incomplete
For a broader approach, use a single ClusterRole/ClusterRoleBinding.	Incomplete
In both scenarios, the CRD remains enabled, and no branching logic is required in the operator.	Incomplete