Incorrect IP address being assigned to Kubernetes Clusters table during Kubernetes pattern executionDescriptionKubernetes Pattern:Step 3.6 -we issue the NSLOOKUP Command and we get back 2 IP addresses from the command result:1. DNS Server IP2. Kubernetes IPStep 4 - we parse ips[1].ip to create the ip_address of the cluster **Unfortunately the element that we are parsing from the array returned by the command in Step 3.6 is actually the DNS Server IP and not the IP of the Kubernetes cluster. This results in every Kubernetes Cluster CI having the IP Address of the DNS Server, which of course, will result in more than likely the same CI being written over and over again with the wrong IP Address.Steps to Reproduce Run a Discovery on a Kubernetes Cluster IP AddressWorkaroundIn Step 4 of the Kubernetes Pattern, modify the step and change: ips[1].ip to: ips[2].ipRelated Problem: PRB1501514