Proposal

After the last months, we have improved a lot the add-on. In order to not lose the momentum, I'd like to define what we would expect from the add-on before considering it in GA, let's track all the features that we think are mandatory and nice to have.

Disclaimer: Currently, these points are just a dump of my thoughts and not a real roadmap, we can add/edit/remove all the items but just for having a starting point

Required

• Define the scope of the project for the mid/long term, do we want to go in service mesh direction?
  • Epic - Support for autoscaling based on traffic flow #350
  • Support rewrote targets during path based routing #851
• Active contributors/maintainers apart from us
• Observability for all the components #965
• KEDA's security standards (signing images, snyk, etc...) #1062
• Versioned docs KEDA HTTP Addon documentation keda-docs#548
• feat: Support aggregation options #961
• Review and update contributors docs
• HTTPScaledObject reconciler not following best practices #611
• Revisit CRD Status conditions (and reason, messages, etc...) #902

Nice to have

• Support using your own scaleobject with more metrics feat: provide support to allow HTTP scaler to work alongside other core KEDA scalers #929
• Support HTTPScaledObject scoped timeout #813
• Use certificates to encrypt internal communications
• Use the external push gRPC protocol for external scaler => interceptor communication #97
• Interceptor Proxy Support for Websockets #654
• Enable dedicated interceptor/scalers with the same operator #241
• "Please hold" landing pages for slow scale from zero scenarios #874
• Load tests
• TLS Support Interceptor Proxy - TLS On The Wire #907
• Proxy letting through too many requests before additional replicas ready  #1038