Description of problem:

In some pod definitions, the CPU/memory Limits and Requests are not set for each container (including init-container). 

Prerequisites (if any, like setup, operators/versions):

Steps to Reproduce

1. From Workloads > Pods section open one pod belonging to RHODS namespaces
2. check the containers in the "Containers" section
3. Go to YAML tab
4. Search for Limits and/or Requests keywords
5. Check if each container (pt. 2) has its own limits/requests

Actual results:

Limits and Requests not specified for each container

Expected results:

CPU and memory limits/requests found for each container

Reproducibility (Always/Intermittent/Only Once):

Always

Build Details:

v.1.1.1-21

Additional info:

An example of pod where all the containers have limits/requests is grafana (namespace: redhat-ods-monitoring) which has three containers and three pairs of limits/requests:

• dashboard-discovery
• grafana
• auth-proxy

While two examples of pods with missing container limits/request are prometheus (namespace: redhat-ods-monitoring) and jupyterhub-1 (namespace: redhat-ods-applications)

This bug is related to this story: https://issues.redhat.com/browse/RHODS-809