In order to get Camel K into the hands of as many users as possible we want to onboard Camel K into Dev Sandbox.

This removes the barrier of setting up OpenShift to the user.

The onboarding process requires Performance Testing.

 
The guide for onboarding new Operators into the sandbox:
https://docs.google.com/document/d/1EI4smiQVOwp0pSic74KIk-SEGASA_nL1gEGdNwH8hnA/edit
 
"As mentioned above, each Developer Sandbox cluster has a capacity of up to 3K users. Each user has 2 namespaces. Users are expected to create workloads (deployments, pods, etc.).
As a result the Sandbox clusters have large numbers of kube/openshift resources. There are up to 10K namespaces, up to 100K rolebindings, dozens/hundreds of thousands of secrets, config maps, thousands of pods, deployments, build configs etc per cluster. The operator should handle such load without consuming too much compute resources, otherwise this may compromise the clusters’ stability."

https://source.redhat.com/groups/public/appservices/wiki/performance_of_service_binding_operator_in_developer_sandbox