Enhancement to k8s pattern based on BMO escalation - Known Error

Enhancement to k8s pattern based on BMO escalation Description Below list of points introduced

Create relations between workloads/dep_conf and services using selectors. Store selectors in 'selector' column of kubernetes service table. Store network_ready and owner_kind in pods table. Properly set updated replicas, desired replicas, available replicas, total replicas and unavailable replicas in replication controllers/ replicasets Set the image id and digest properly for docker images in kubernetes pattern. Store the docker image name from the repo tag in kubernetes pattern Adjust container repository extension to store repository info properly Align the docker container id in K8s pattern with that in docker pattern Capture 'Cronjob' and 'Job' type kubernetes workloads. Steps to Reproduce

Verify that services are related to workloads(deployments, statefulsets, daemonsets) and deployment config(openshift). Verify that the label selectors specified in the service configuration for selecting pods are captured in the 'selector' column as string of comma separated values. owner_kind stores the workload type that owns a kubernetes pod. - 'Replicationcontroller', 'Replicaset', etc. network_ready is a boolean value that marks if a pod is ready for communicating with a service. The output of (/endpoints) api lists pods that are not ready for networking under the field 'notReadyAddresses'. Verify that the pods listed under 'notReadyAddresses' field have a value of false for 'network_ready' column. Test if the values for the listed columns are populated accurately in every case (populated value should be 0 if the field value is null in API response) Image ID should be the first 12 characters of the digest. The docker image name should be populated from the repo to which it belongs. Verify that container repository for a docker image is captured. The docker container id should be the first 12 characters of its digest. Verify that 'Job' and 'Cronjob' type workloads are captured during discovery. Cronjobs should be related to cluster, namespaces and jobs. Jobs should be related to cluster, namespaces, cronjobs and pods. Workaround This problem has been fixed. If you are able to upgrade, review the Fixed In or Intended Fix Version fields to determine whether any versions have a planned or permanent fix.