feat: New ScalingSet CRD to deploy isolated interceptors+scalers

[kahirokunn]

Provide a description of what has been changed

kedacore/http-add-on#1014

Checklist

• I have verified that my change is according to the deprecations & breaking changes policy
• Commits are signed with Developer Certificate of Origin (DCO - learn more)
• README is updated with new configuration values (if applicable) learn more
• A PR is opened to update KEDA core (repo) (if applicable, ie. when deployment manifests are modified)
  • feat: New ScalingSet CRD to deploy isolated interceptors+scalers http-add-on#1014

Fixes #

[Farfaday]

Please add the crds.additionalAnnotations to the new CRDs.
By copying this block for example: https://github.com/kedacore/charts/blob/main/keda/templates/crds/crd-scaledjobs.yaml#L7
Thanks!

[kahirokunn]

@Farfaday Thank you for your review! I have implemented all of the points you raised in your review.

[imdmahajankanika]

Hello! Is this feature about creating interceptor svc in the same namespace as application rather than KEDA namespace?

[kahirokunn]

Yes, that's correct! This feature allows for creating an interceptor service in the same namespace as the application. Additionally, it also supports creating a shared interceptor service if desired.

[imdmahajankanika]

Yes, that's correct! This feature allows for creating an interceptor service in the same namespace as the application. Additionally, it also supports creating a shared interceptor service if desired.

Thanks! So that means, instead of creating a service of type external name for interceptor service in the application namespace, I can directly connect ingress to the interceptor service in the application namespace.