How to enable resource management in kurtosis with kubernetes backend?

[barnabasbusa]

Resource management is a huge benefit of kubernetes. Automatic up/down scaling based on current CPU/RAM usage is one of the main reason people choose to go with kubernetes the first place.

Is it already possible to configure kurtosis with specific resource requests and limits for specific pods?

example:

    resources:
      requests:
        memory: "64Mi"
        cpu: "250m"
      limits:
        memory: "128Mi"
        cpu: "500m"

If its not yet possible, it would be great to be able to individually limit/request resources based on the different client combination you are running. E.g you might want to give more RAM but less CPU for a besu node.

Without requests/limits, autoscaling in the cloud is not going to be possible.

While talking about resource limits, its also worth mentioning that docker has similar ways to limit specific containers to specific amount of resources. So this could be handled at the same time, using the same flags configured in starlark.

[h4ck3rk3y]

@barnabasbusa you can set the minimum and maximum resources for k8s nodes via - https://docs.kurtosis.com/starlark-reference/service-config/

Haven't added support for this to the eth-network-package package yet but this would involve tweaking service config

[barnabasbusa]

Would be great if this resource limit could be configured in the json config file. For example:

{
  "participants": [
    {
      "el_client_type": "geth",
      "el_client_image": "ethpandaops/geth:4844-devnet-6-e03b5ad",
      "cl_client_type": "lighthouse",
      "cl_client_image": "ethpandaops/lighthouse:boxed-blobs-d534ac0",
      "cpu": "100","1000",
      "ram": "512","2048",
      "count": 2
    }
  ],
  "network_params": {
    "deneb_fork_epoch": 3
  },
  "launch_additional_services": true,
  "wait_for_finalization": false,
  "wait_for_verifications": false,
  "global_client_log_level": "info"
}

or something similar

[mieubrisse]

Hey @barnabasbusa , what do you think about submitting a PR for this? Should be super simple - just piping from the args-parsing down through the participant network and into the ServiceConfig of each of the clients (e.g. here is Lighthouse's)

[barnabasbusa]

Will look into it.

[mieubrisse]

Sounds good! Let us know if you hit any issues

[leeederek]

For posterity, I am linking kurtosis-tech/eth-network-package#64 where @barnabasbusa, following this conversation, was able to add Resource Management to the package he has been using.

[mieubrisse]

Very nice @barnabasbusa !!