Kubernetes serveless execution pattern takes a long time to execute which often leads to discovery status getting cancelledDescriptionKubernetes serverless execution pattern based Discovery schedule takes a long to execute and process and as a result it get's cancelled often.Steps to Reproduce This was reproducible in a customer env.1)create discovery schedule with Kubernetes serveless execution pattern.2)Try to discover any known kubernetes namespace which has lot of POD's deployed(more than 200) and while running discovery it will be noticed that the discovery gets cancelled.WorkaroundThe Pattern changes that fix the performance issue are in November release of the "Discovery and Service Mapping Patterns" plugin. The fix consists of the following two steps: 1 Changing all JSON parsing to new custom operation JSON parse2 Modified all relations (for example, removed relation between cmdb_ci_kubernetes_pod to cmdb_ci_kubernetes_service), and merged steps to use 1 condition where possible, because using 2 or more has huge performance impact if the tables are hugeRelated Problem: PRB1519897