Changes upon Kubernetes main pattern and related patterns (shared libraries), and relationships steps optimisationDescriptionIn relation to multiple customer issues raised, several changes are introduced in the context of discovery pattern "Kubernetes" part of plugin "Discovery and Service Mapping Patterns": 1. "Kubernetes discovery is successful, however Kubernetes Volume, Linux Server and Openshift components are not populated during discovery" 2. "Kubernetes discovery failed with error "MID Server received a large response that exceed the allowed number of rows 1,000,000" 3. "Kubernetes pattern is not building relation for Kubernetes Node to Linux server"Steps to Reproduce 1. Trigger discovery schedule against Kubernetes environment 2. Notice that several issues are encounteredWorkaroundChanges upon the following patterns are in place: Kubernetes main patternKubernetes PodKubernetes Phys NodeKubernetes Image Where logical conditions are changed, optimisation of relationship steps are done. The changes will be released Out of the Box in relation to PRB1559582. And available in the middle of May 2022 as part of plugin "Discovery and Service Mapping Patterns" version 1.0.90 a) Changes related to main pattern "Kubernetes" - pattern step introduced: "transform pods table for relation with volumes" - pattern step introduced: "transform volume table for relation to pods" - Optimised relationship in pattern step "relation to cmdb_ci_kubernetes_pod" b) Changes related to shared library "Kubernetes Pod" - pattern step introduced: "parsing pods label data" - pattern step introduced: "safety parsing for pods" c) Changes related to shared library "Kubernetes Phys Node" - pattern step introduced: "get nodes physical info" d) Changes related to shared library "Kubernetes Image" - Modification in pattern step "remove duplicates for final images forming"Related Problem: PRB1559582