Liqo Controller, Metrics Agent, Virtual Kubelet resource usage is too much

[Sharathmk99]

What happened:

In our production environment we are observing below liqo services Memory usage is crazy in remote cluster,

• Controller
• Metrics Agent
• Virtual Kubelet

1. Controller

2. Metrics Agent(this is crazy)

3. Virtual Kubelet

There are 7282 active pods reflected to remote cluster.

k get shadowpods.virtualkubelet.liqo.io -A | wc -l
7282

But it doesn't look bad on local cluster, but remote is crazy.

Is this expected, if yes how can we scale?

Can we know what's the role of metrics-agent in liqo deployment?

What you expected to happen:

Low memory usage of liqo services.

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

Environment:

• Liqo version: latest
• Liqoctl version:
• Kubernetes version (use kubectl version): 1.24
• Cloud provider or hardware configuration: on-premises
• Node image:
• Network plugin and version:
• Install tools:
• Others: