Display resource configuration that is effective on the function's runtime pod

[kwiatekus]

Description

Show the actual cpu and memory units configured on the runtime pod in the status of the function and in kyma dashboard.
Currently we expose only the applied profile ( in the status ) but this information is nowhere shown in the UI.
Additionally it lacks the concrete units information and the resources allocated for the istio side car.
It would make sense for function controller to inspect the overal resources of all containers of the runtime pod and expose this information in the function status. Furter on, this information should be shown in the UI

AC

• function status shows request and limits of all the containers (incl. istio proxy) of the runtime pod
• details view of the function present this information in the kyma dashboard

Reasons
There are many ways how user can set function runtime resources:

• set profile (S,M,L,etc)
• set custom resource configuration values
• leave everything empty and have the default preset set by the controller.

We are missing a way of displaying resources that would be working for all those 3 ways and that would include also resources originating from eventual istio side cart container.

This makes the user totally unaware about the total amount of resources used by his function.

We are showing applied profiles, for instance:

status:
  buildResourceProfile: fast
  functionResourceProfile: L

But we show no actually applied cpu or memory units that user can refer to (see attachment).

Attachments

[kyma-bot]

This issue or PR has been automatically marked as stale due to the lack of recent activity.
Thank you for your contributions.

This bot triages issues and PRs according to the following rules:

• After 60d of inactivity, lifecycle/stale is applied
• After 7d of inactivity since lifecycle/stale was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Close this issue or PR with /close

If you think that I work incorrectly, kindly raise an issue with the problem.

/lifecycle stale