Aggregation of Container Metric Data

[shreyabiradar07]

Description

This PR has the following changes:

• Aggregates the metric data and calculates the avg, min, max values based on the container experiment to generate recommendations
• The data comes from the individual queries in local monitoring mode PR 1359

Steps to generate recommendations for container and namespace openshift-apiserver- https://privatebin.corp.redhat.com/?7ed7bfc48564d285#fpUsX7rhx2c6fL5HufqdJCRQJsQpMzs32HYb8aKA7Jc

After generating recommendations, either of the below steps can be followed to verify the aggregation of individual query data

1. Using kruize pod logs

• Input CSV file with metric data for each pod is logged under - Contents of input.csv:
• Aggregated Output CSV file is logged under - Contents of output.csv:

2. Using kubectl exec to access CSV files inside the pod

• Exec into Kruize pod:
  kubectl exec -it <kruize-pod> -n openshift-tuning -- /bin/bash
• pwd
  /home/autotune/app
• ls
  input.csv jre output output.csv target

NOTE: PR currently has added logs for verifying the aggregation of data, once reviewed will be removed before merging

Type of change

• Bug fix
• New feature
• Docs update
• Breaking change (What changes might users need to make in their application due to this PR?)
• Requires DB changes

How has this been tested?

Please describe the tests that were run to verify your changes and steps to reproduce. Please specify any test configuration required.

• New Test X
• Functional testsuite

Test Configuration

• Kubernetes clusters tested on: ResourceHub, Openshift

Checklist 🎯

• Followed coding guidelines
• Comments added
• Dependent changes merged
• Documentation updated
• Tests added or updated

Additional information

docker image: quay.io/shbirada/metric_data_aggr:v1