Data sources do not show up in the CP4S Connections page

Resolving The Problem

1. To immediately resolve the issue, delete the udi-udiendpoints-xxxxxxxx-xxxx with the Red Hat OpenShift oc command-line tool:

   oc delete pod udi-udiendpoints-xxxxxxxx-xxx udi-udiendpoints-xxxxxxxx-xxx
   pod "udi-udiendpoints-xxxxxxxx-xxx" deleted
   pod "udi-udiendpoints-xxxxxxxx-xxx" deleted
   
           

2. Once the udi-udiendpoints pods show as Running, the data sources are now present on the Connections page.

   udi-udiendpoints-xxxxxxx-xxxxxx                                 1/1     Running     0          16d
   udi-udiendpoints-xxxxxxx-xxxxxx                                 1/1     Running     0          16d
   
           

3. The command previously run will not permanently resolve the issue as the data sources can disappear again after some time. These next steps can limit the number of times this issue occurs by giving the redis pods more CPU resources.
   To increase the CPU resources for the redis pods:

    kubectl edit iscinventory redis-default 
       server:
        limits:
         cpu: 200m <- change to 1000m
         memory: 1Gi
        requests:
         cpu: 500m
         memory: 200Mi
    
           

   NOTE: Where 1000m = 1 CPU core. For example, if a node has 2 cores, the node's CPU capacity would be represented as 2000m. If you wanted to use one-tenth of a single core, it would be represented as 100m. It is only recommended to increase it to 1000m as anything higher might result in unexpected behavior with the pod.
    
4. Delete the cp4s-helper-operator pod:

   oc delete pod cp4s-helper-operator-xxxxxxxx
   
           

5. Then, delete the redis pods:

   oc get pod -o name | grep redis | xargs oc delete