chuck-bear
chuck-bear
This is still an issue Today. Is there anyone working on it?
yeah I made it work by using Grafana agent.
@nidhi-singh02 to recover the pods you can run this: ``` # When you have killed a pod, restart it with that command: kurtosis service start my-local-devnet cl-validator-beaconkit-0 ```
`cl-validator-beaconkit-0` is the name of the component that you have killed
> Thanks @chuck-bear! I believe recovery should happen automatically (without our manual intervention). I have few related queries on the same behaviour, wanted to understand the current setup - >...
https://github.com/crytic/attacknet/issues/64 for the recovery.
I tested the pod restarts scenario and used the `--production` flag to allow pod restart. For example: ``` start-devnet-no-build-gcp: kurtosis run ./kurtosis --args-file ./kurtosis/beaconkit-base-gcp.yaml \ --enclave my-gcp-devnet --production ```
The go packages here https://github.com/crytic/attacknet/releases could be used for that.
https://github.com/CharlesJUDITH/tmkms-helm-chart
@camembera I confirm that this won't matter for anything in infra