[Epic] Extend Amun feature wise to be a testing platform for containers in a cluster

[fridex]

Is your feature request related to a problem? Please describe.

As a developer, I would like to know how applications that are deployed into the cluster behave from different aspects so that I can observe what is happening to my application based on statistics produced by the service.

As a data scientist, I would like to have a unified report that can be analyzed from different points of view so that I can sport possible issues with the container image deployed in the cluster. To support this, I would like to have an ability to reuse jupyter notebooks that can automatically load reports produced by the service.

As we already have deployment and core features of amun in place, this is more about abstracting out some features and eventually provide more, such as GPU utilization for the container when it is run in a cluster.

Workflow:

1. User submits Amun inspection with a pre-built container image respecting configuration supplied (node placement in the cluster, GPU requirements, CPU requirements, ...)
2. Amun runs the application in a way user requests to do it (e.g. run a training phase of a machine learning model)
3. Amun captures runtime statistics of the application (CPU utilization, process statistics from the PCB, GPU utilization, networking, ...) and reports them as a JSON
4. A prepared jupyter notebook is used to automatically visualize statistics to users
5. Users can spot issues, discrepancies, or other runtime characteristics from the report to analyze the application behavior in the cluster

[goern]

/kind feature
/triage needs-information
/area amun
/area knowledge-graph

[sesheta]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

[sesheta]

@sesheta: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[fridex]

/reopen
/remove-lifecycle rotten

[sesheta]

@fridex: Reopened this issue.

In response to this:

/reopen
/remove-lifecycle rotten

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[goern]

/lifecycle frozen

[codificat]

/triage accepted
/priority backlog

[codificat]

From today's backlog refining now this might require some additional research on what/if/how to proceed.

Focus would be on the generated, user-facing and user accessible report.

/remove-triage accepted
/triage needs-information
/sig user-experience